Triple
T3870906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Artery |
E91981
|
entity |
| Predicate | designChallenge |
P51588
|
FINISHED |
| Object | limited right-of-way in downtown Boston |
—
|
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: limited right-of-way in downtown Boston | Statement: [Central Artery, designChallenge, limited right-of-way in downtown Boston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designChallenge Context triple: [Central Artery, designChallenge, limited right-of-way in downtown Boston]
-
A.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
-
B.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
C.
engineeringGoal
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
D.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
E.
missionDesign
Indicates the relationship in which an entity plans, structures, and specifies the objectives, constraints, and procedures for carrying out a mission.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec54b0848190a8d4a0e4df7b6227 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.