Triple
T34425668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondo neighborhood |
E883659
|
entity |
| Predicate | hasPlanningDiscussion |
P193853
|
FINISHED |
| Object | proposals for a land bridge over I-94 |
—
|
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: proposals for a land bridge over I-94 | Statement: [Rondo neighborhood, hasPlanningDiscussion, proposals for a land bridge over I-94]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningDiscussion Context triple: [Rondo neighborhood, hasPlanningDiscussion, proposals for a land bridge over I-94]
-
A.
hasPlanningSignificance
Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
-
B.
hasPlanningConcept
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
C.
hasPlanningIssue
Indicates that an entity is associated with a problem, concern, or complication related to planning or plan formulation.
-
D.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
E.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 1, 2026, 2 a.m.