Triple
T35511050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railroad (Fallout 4) |
E1026285
|
entity |
| Predicate | questlineName |
P184431
|
FINISHED |
| Object | The Railroad quests |
—
|
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: The Railroad quests | Statement: [Railroad (Fallout 4), questlineName, The Railroad quests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questlineName Context triple: [Railroad (Fallout 4), questlineName, The Railroad quests]
-
A.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
B.
questlineAvailableIn
Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
-
C.
questName
Indicates the specific title or identifier assigned to a quest within a game or narrative system.
-
D.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
E.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
- 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_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:04 p.m.