Triple
T37423102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roncesvalles streetcar routes |
E929914
|
entity |
| Predicate | runAlong |
P188064
|
FINISHED |
| Object | Roncesvalles Avenue |
—
|
NE NERFINISHED |
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: Roncesvalles Avenue | Statement: [Roncesvalles streetcar routes, runAlong, Roncesvalles Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runAlong Context triple: [Roncesvalles streetcar routes, runAlong, Roncesvalles Avenue]
-
A.
runsDirection
Indicates that an entity moves or operates in a specified direction.
-
B.
run
Indicates that an entity moves swiftly on foot, typically by taking rapid steps so that both feet are off the ground at some points.
-
C.
ranOn
Indicates that an entity executed or operated on a particular platform, system, or environment.
-
D.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
E.
ranIn
Indicates that an entity performed a running action within or during a specified location, context, or time frame.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.