Triple
T35511057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railroad (Fallout 4) |
E1026285
|
entity |
| Predicate | usesCoverNameForSynths |
P21109
|
FINISHED |
| Object | "agents" |
—
|
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: "agents" | Statement: [Railroad (Fallout 4), usesCoverNameForSynths, "agents"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoverNameForSynths Context triple: [Railroad (Fallout 4), usesCoverNameForSynths, "agents"]
-
A.
hasCoverName
chosen
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
B.
coverName
Indicates that one entity serves as an alternative, alias, or substitute name used to represent or refer to another entity.
-
C.
isCoverFor
Indicates that one entity serves as a protective or concealing layer, substitute, or front for another entity or activity.
-
D.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
E.
hasCoverVersionPerformer
Indicates that an entity is the performer of a cover version of another entity’s original work.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:04 p.m.