Triple
T34989032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vault 76 |
E1009330
|
entity |
| Predicate | reclamationDayYear |
P182176
|
FINISHED |
| Object | 2102 |
—
|
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: 2102 | Statement: [Vault 76, reclamationDayYear, 2102]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclamationDayYear Context triple: [Vault 76, reclamationDayYear, 2102]
-
A.
reclamationStartDate
Indicates the date on which a reclamation process or activity is initiated.
-
B.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
C.
recoveredYear
Indicates the year in which something that was lost, damaged, or unwell was successfully restored, retrieved, or brought back to a desired state.
-
D.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
E.
reclamationPeriod
Indicates the time span during which something that was previously taken, lost, or deactivated can be recovered or restored.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.