Triple
T35009419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost Hills bunker |
E1009904
|
entity |
| Predicate | factionOccupant |
P71829
|
FINISHED |
| Object | Brotherhood of Steel |
—
|
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: Brotherhood of Steel | Statement: [Lost Hills bunker, factionOccupant, Brotherhood of Steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionOccupant Context triple: [Lost Hills bunker, factionOccupant, Brotherhood of Steel]
-
A.
enemyOccupation
Indicates that a location or territory is currently controlled or held by enemy forces.
-
B.
factionRole
Indicates the specific role, function, or position an entity holds within a particular faction or group.
-
C.
occupyingForces
chosen
Indicates that one group’s military forces are present in and exercising control over a territory that is not their own, typically without the full consent of the local sovereign authority.
-
D.
occupationForcesCommandedBy
Indicates that a particular occupation force is under the command or authority of a specified commander or commanding entity.
-
E.
factionType
Indicates the classification or category of a faction within a broader system or context.
- 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_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.