Triple
T28048673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Artery corridor |
E708757
|
entity |
| Predicate | placedUndergroundDuring |
P176300
|
FINISHED |
| Object | 1990s–2000s |
—
|
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: 1990s–2000s | Statement: [Central Artery corridor, placedUndergroundDuring, 1990s–2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placedUndergroundDuring Context triple: [Central Artery corridor, placedUndergroundDuring, 1990s–2000s]
-
A.
integratedIntoUnderground
Indicates that something has been incorporated or absorbed into an underground system, structure, or environment.
-
B.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
C.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
D.
wasTrappedUndergroundFor
Indicates that an entity was confined beneath the ground for a specified duration or period.
-
E.
excavatedUnder
Indicates that one entity was dug out, uncovered, or removed from beneath another entity during an excavation process.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 27, 2026, 8:31 p.m.