Triple
T25064487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BaltimoreLink |
E627744
|
entity |
| Predicate | planningIncluded |
P21551
|
FINISHED |
| Object | bus stop consolidation |
—
|
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: bus stop consolidation | Statement: [BaltimoreLink, planningIncluded, bus stop consolidation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningIncluded Context triple: [BaltimoreLink, planningIncluded, bus stop consolidation]
-
A.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
B.
planningProcessIncludes
chosen
Indicates that a broader planning process encompasses or contains a specific sub-process, step, or activity as one of its components.
-
C.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
D.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
E.
planningSupport
Indicates that one entity provides assistance, resources, or guidance to another in the process of planning or preparing for something.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:10 a.m.