Triple
T3607735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MA 129 |
E76412
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object |
Route 38
Route 38 is a state highway in Massachusetts that serves as a regional connector through several communities north of Boston.
|
E372745
|
NE FINISHED |
How this triple was built (4 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: Route 38 | Statement: [MA 129, hasJunctionWith, Route 38]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Route 38 Context triple: [MA 129, hasJunctionWith, Route 38]
-
A.
Route 38
Route 38 is a major east–west state highway in southern New Jersey that serves as a key commercial and commuter corridor through Cherry Hill and surrounding communities.
-
B.
Route 36
Route 36 is a SEPTA subway–surface trolley line in Philadelphia that provides light rail service between Center City and Southwest Philadelphia.
-
C.
Route 31
Route 31 is a major north–south state highway in New Jersey that connects several central and northwestern communities, serving as a key regional transportation corridor.
-
D.
Route 35
Route 35 is a major New Jersey state highway running along the central Jersey Shore and through several urban and suburban communities.
-
E.
Route 34
Route 34 is a SEPTA subway–surface trolley line in Philadelphia that runs between Center City and West Philadelphia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Route 38 Triple: [MA 129, hasJunctionWith, Route 38]
Generated description
Route 38 is a state highway in Massachusetts that serves as a regional connector through several communities north of Boston.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Route 38 Target entity description: Route 38 is a state highway in Massachusetts that serves as a regional connector through several communities north of Boston.
-
A.
Route 38
Route 38 is a major east–west state highway in southern New Jersey that serves as a key commercial and commuter corridor through Cherry Hill and surrounding communities.
-
B.
Route 36
Route 36 is a SEPTA subway–surface trolley line in Philadelphia that provides light rail service between Center City and Southwest Philadelphia.
-
C.
Route 31
Route 31 is a major north–south state highway in New Jersey that connects several central and northwestern communities, serving as a key regional transportation corridor.
-
D.
Route 35
Route 35 is a major New Jersey state highway running along the central Jersey Shore and through several urban and suburban communities.
-
E.
Route 34
Route 34 is a SEPTA subway–surface trolley line in Philadelphia that runs between Center City and West Philadelphia.
- F. None of above. chosen
Provenance (5 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc228e24481909ae6a1e4ad796917 |
completed | March 8, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4330bc9f081909a5c1e6da885cfc5 |
completed | March 13, 2026, 3:53 p.m. |
| NEDg | Description generation | batch_69b4364e9f848190ab1e5e03c43dfae4 |
completed | March 13, 2026, 4:07 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b4367bec908190b0c6dc844af5e366 |
completed | March 13, 2026, 4:08 p.m. |
Created at: March 8, 2026, 3:22 p.m.