Triple
T30538852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Line |
E777220
|
entity |
| Predicate | widthPlanned |
P619
|
FINISHED |
| Object | about 200 meters |
—
|
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: about 200 meters | Statement: [The Line, widthPlanned, about 200 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widthPlanned Context triple: [The Line, widthPlanned, about 200 meters]
-
A.
plannedHeight
Indicates the intended or designed vertical size or elevation that something is planned to have.
-
B.
plannedLength
Indicates the intended or scheduled duration or size of something as determined in advance, rather than its actual or realized extent.
-
C.
width
chosen
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
widthFeet
Indicates the measurement of an object's width expressed in feet.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f688531c808190ad82e2ef22e0e9a7 |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:19 p.m.