Triple
T2257813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dupont Circle station |
E49766
|
entity |
| Predicate | hasDepth |
P36777
|
FINISHED |
| Object | deep-level underground station |
—
|
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: deep-level underground station | Statement: [Dupont Circle station, hasDepth, deep-level underground station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepth Context triple: [Dupont Circle station, hasDepth, deep-level underground station]
-
A.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
B.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
-
C.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
D.
isDeeperThan
Indicates that one entity has a greater depth or is positioned further down than another entity.
-
E.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc15839fc8190b17e040c4c765a8c |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:48 p.m.