Triple
T23921279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Route 18 |
E602219
|
entity |
| Predicate | roleInNewBedford |
P8234
|
FINISHED |
| Object | primary north–south urban expressway |
—
|
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: primary north–south urban expressway | Statement: [Massachusetts Route 18, roleInNewBedford, primary north–south urban expressway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNewBedford Context triple: [Massachusetts Route 18, roleInNewBedford, primary north–south urban expressway]
-
A.
roleInNewJersey
Indicates that an entity holds or held a specific role, position, or function within the state of New Jersey.
-
B.
roleInLyndhurst
Indicates that an entity holds or held a specific role or position within the context of Lyndhurst.
-
C.
isNewEnglandTown
Indicates that the subject is a town located within the New England region.
-
D.
roleInAddressing
Indicates the specific function or responsibility an entity has in dealing with or responding to a particular issue, situation, or task.
-
E.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
- F. None of above.
Provenance (3 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf18d99081908efc0251ef6f25a5 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:41 p.m.