Triple
T18473344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Awaza Station |
E451358
|
entity |
| Predicate | hasStationCodeOnLine |
P1289
|
FINISHED |
| Object | C15 |
—
|
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: C15 | Statement: [Awaza Station, hasStationCodeOnLine, C15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationCodeOnLine Context triple: [Awaza Station, hasStationCodeOnLine, C15]
-
A.
hasStationCode
chosen
Indicates that an entity is associated with a specific station identification code.
-
B.
hasStationCodeSystem
Indicates that an entity uses or is associated with a particular system for assigning or managing station codes.
-
C.
hasStationCodeInternal
Indicates that an entity is associated with a specific internal station code used within a system or organization.
-
D.
isPassengerStationCode
Indicates that a given code is officially assigned to identify a particular passenger station.
-
E.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e530617e48819091240d4405e53aaa |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.