Triple
T30057431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canal Streetcar Line |
E763769
|
entity |
| Predicate | runsMostlyAlong |
P103871
|
FINISHED |
| Object | Canal Street median |
—
|
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: Canal Street median | Statement: [Canal Streetcar Line, runsMostlyAlong, Canal Street median]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsMostlyAlong Context triple: [Canal Streetcar Line, runsMostlyAlong, Canal Street median]
-
A.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
-
B.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
C.
runsDirection
Indicates that an entity moves or operates in a specified direction.
-
D.
runsPrimarilyThrough
chosen
Indicates that one thing is mainly routed, conducted, or passes through another thing as its primary path or channel.
-
E.
runMostlyAt
Indicates that an activity, process, or entity operates primarily or for the most part at a particular time, place, or condition.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:56 p.m.