Triple
T35511051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railroad (Fallout 4) |
E1026285
|
entity |
| Predicate | factionEndingAvailable |
P184646
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Railroad (Fallout 4), factionEndingAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionEndingAvailable Context triple: [Railroad (Fallout 4), factionEndingAvailable, yes]
-
A.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
-
B.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
C.
alternateEnding
Indicates that one version of a work provides a different conclusion or final sequence of events compared to the original or primary ending.
-
D.
canConclude
Indicates that one entity is able to logically derive or reach a conclusion about another entity or situation.
-
E.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
- F. None of above. chosen
Provenance (4 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:04 p.m.