Triple
T19232415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E Embarcadero line |
E480902
|
entity |
| Predicate | heritageStreetcarsOrigin |
P135285
|
FINISHED |
| Object | various U.S. cities |
—
|
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: various U.S. cities | Statement: [E Embarcadero line, heritageStreetcarsOrigin, various U.S. cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageStreetcarsOrigin Context triple: [E Embarcadero line, heritageStreetcarsOrigin, various U.S. cities]
-
A.
hasStreetcarHistory
Indicates that there is a historical association or past involvement with streetcars or streetcar systems.
-
B.
historicRacingCar
Indicates that an entity is a racing car of historical significance, typically from a past era of motorsport competition.
-
C.
hasHistoricStreetcarsDisplayed
Indicates that historic streetcars are present and exhibited at a location or facility.
-
D.
heritageStyle
Indicates that one entity is characterized by, designed in, or associated with a particular heritage or traditional style defined by the other entity.
-
E.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9db56081908f50d318d7fc9eaa |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:25 p.m.