Triple
T34989034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vault 76 |
E1009330
|
entity |
| Predicate | inUniverseConstructionEra |
P179948
|
FINISHED |
| Object | pre–Great War |
—
|
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: pre–Great War | Statement: [Vault 76, inUniverseConstructionEra, pre–Great War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseConstructionEra Context triple: [Vault 76, inUniverseConstructionEra, pre–Great War]
-
A.
inUniversePeriod
chosen
Indicates that something exists, occurs, or is valid within a specified time period in a particular fictional or conceptual universe.
-
B.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
C.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
-
D.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
E.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:01 p.m.