Triple
T2036623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY 202 |
E44644
|
entity |
| Predicate | sharesCorridorWith |
P35459
|
FINISHED |
| Object | US 6 in parts of its length |
—
|
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: US 6 in parts of its length | Statement: [NY 202, sharesCorridorWith, US 6 in parts of its length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCorridorWith Context triple: [NY 202, sharesCorridorWith, US 6 in parts of its length]
-
A.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
B.
sharesTrunkWith
Indicates that two entities have a common trunk or main stem from which they both extend or branch.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesBuildingWith
Indicates that two entities occupy or use the same building.
-
E.
sharesComponentsWith
Indicates that two entities have one or more structural or functional components in common.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9363b608190b42aa6d3f3fd78c4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:39 p.m.