Triple
T30487870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTfastrak |
E775769
|
entity |
| Predicate | corridorEndpoints |
P169497
|
FINISHED |
| Object | New Britain |
—
|
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: New Britain | Statement: [CTfastrak, corridorEndpoints, New Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corridorEndpoints Context triple: [CTfastrak, corridorEndpoints, New Britain]
-
A.
corridorEndApprox
Indicates that one location is approximately at or near the end of a corridor relative to another location.
-
B.
corridorStartApprox
Indicates an approximate or estimated starting point of a corridor in relation to another spatial element or reference.
-
C.
numberOfCorridors
Indicates the total count of corridors associated with or contained within a given entity or structure.
-
D.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate system.
-
E.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687470d308190897ede84a93ad4f2 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:13 p.m.