Triple
T1293122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minuteman Bikeway |
E27591
|
entity |
| Predicate | openedSegment |
P28341
|
FINISHED |
| Object | Arlington–Lexington segment opened 1992 |
—
|
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: Arlington–Lexington segment opened 1992 | Statement: [Minuteman Bikeway, openedSegment, Arlington–Lexington segment opened 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedSegment Context triple: [Minuteman Bikeway, openedSegment, Arlington–Lexington segment opened 1992]
-
A.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
-
B.
openedInPart
Indicates that an entity was opened or made accessible only partially, rather than fully or completely.
-
C.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
D.
openedAfter
Indicates that one entity was opened at a later time than another entity.
-
E.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c3b9ebdc819098de4d3288201bc1 |
completed | March 1, 2026, 10:54 p.m. |
Created at: March 1, 2026, 7:51 p.m.