Triple
T31375349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Route 43 |
E800281
|
entity |
| Predicate | terminusWestState |
P179830
|
FINISHED |
| Object | New York |
—
|
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 York | Statement: [Massachusetts Route 43, terminusWestState, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusWestState Context triple: [Massachusetts Route 43, terminusWestState, New York]
-
A.
terminusProvinceWest
Indicates that the western terminus of an entity (such as a route or line) is located within a specified province.
-
B.
terminusWestCountry
Indicates that something serves as the western endpoint or final stop of a route, line, or connection within the West Country region.
-
C.
terminusCityWest
Indicates that a route, line, or service has its western terminus located in the specified city.
-
D.
terminusWestNear
Indicates that the western terminus of one entity is located near the western terminus of another entity.
-
E.
terminusWestConnection
Indicates that one entity serves as the western endpoint where it connects to another entity or route.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 29, 2026, 9:18 p.m.