Triple
T22346439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyohashi |
E552402
|
entity |
| Predicate | tramSystem |
P80172
|
FINISHED |
| Object | Toyohashi Railroad Azumada Main Line |
—
|
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: Toyohashi Railroad Azumada Main Line | Statement: [Toyohashi, tramSystem, Toyohashi Railroad Azumada Main Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tramSystem Context triple: [Toyohashi, tramSystem, Toyohashi Railroad Azumada Main Line]
-
A.
tramSystemName
Indicates the name assigned to a particular tram system.
-
B.
tramOperator
chosen
Indicates that one entity operates, manages, or runs tram services for another entity or area.
-
C.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
D.
tramRoutes
Indicates that there exists a tram line or service that operates along a route connecting the related locations.
-
E.
partOfTransitSystem
Indicates that something is a component or segment within a larger transit or transportation system.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157981c0881909ac74d68b99075c2 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.