Triple
T35137775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallout Tactics: Brotherhood of Steel |
E1014620
|
entity |
| Predicate | hasPlayableRaces |
P98927
|
FINISHED |
| Object | humans |
—
|
LITERAL FINISHED |
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: humans | Statement: [Fallout Tactics: Brotherhood of Steel, hasPlayableRaces, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayableRaces Context triple: [Fallout Tactics: Brotherhood of Steel, hasPlayableRaces, humans]
-
A.
playableRacesHub
Indicates that a given hub, setting, or context supports or includes certain races as playable options.
-
B.
playableRace
chosen
Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
-
C.
hasSupportRaces
Indicates that an entity provides backing, endorsement, or assistance to one or more races (such as competitions or racial groups).
-
D.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
E.
playableRaceForClass
Indicates that a particular race is allowed or eligible to be chosen as a playable option for a given character class.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:02 p.m.