Triple
T34989016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vault 76 |
E1009330
|
entity |
| Predicate | overseerTitle |
P179216
|
FINISHED |
| Object | Overseer of Vault 76 |
—
|
NE NERFINISHED |
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: Overseer of Vault 76 | Statement: [Vault 76, overseerTitle, Overseer of Vault 76]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseerTitle Context triple: [Vault 76, overseerTitle, Overseer of Vault 76]
-
A.
supervisorTitle
chosen
Indicates the formal job title or position held by a person who acts as a supervisor in the relationship.
-
B.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
D.
leaderMayHoldTitle
Indicates that a leader is permitted or able to possess or be designated by a particular formal title.
-
E.
supportedLeaderTitle
Indicates that an entity held a position or title in support of, or subordinate to, a specified leader.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.