Triple
T35009779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Institute (Fallout) |
E1009912
|
entity |
| Predicate | leaderInFallout4 |
P65676
|
FINISHED |
| Object | Father |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Father | Statement: [The Institute (Fallout), leaderInFallout4, Father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderInFallout4 Context triple: [The Institute (Fallout), leaderInFallout4, Father]
-
A.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
B.
leaderUsingHeadquarters
Indicates that a leader conducts their leadership activities or operations from a particular headquarters location.
-
C.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
D.
leader5
Indicates that an entity serves as the primary leader, head, or top authority within a specified group, organization, or context.
-
E.
leaderOfGroup
chosen
Indicates that an entity holds a leadership role or primary authority over a particular group.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:01 p.m.