Triple
T2845891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Triangle station |
E62581
|
entity |
| Predicate | hasVaultType |
P43372
|
FINISHED |
| Object | coffered concrete vault |
—
|
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: coffered concrete vault | Statement: [Federal Triangle station, hasVaultType, coffered concrete vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVaultType Context triple: [Federal Triangle station, hasVaultType, coffered concrete vault]
-
A.
hasGoldVault
Indicates that one entity possesses or contains a vault specifically used for storing gold.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
D.
hasLockType
Indicates that an entity is associated with or uses a specific type or category of lock.
-
E.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf3d00708190966a477fdd855f23 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.