Triple
T19057792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irkutsk Time |
E466443
|
entity |
| Predicate | usedInRailwayTimeContext |
P9621
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Irkutsk Time, usedInRailwayTimeContext, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRailwayTimeContext Context triple: [Irkutsk Time, usedInRailwayTimeContext, yes]
-
A.
railwayTimeUsage
Indicates how much time is spent using or operating a railway within a given context or period.
-
B.
usedForRailwayTimetables
chosen
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
-
C.
usedForCivilTimeIn
Indicates that something (typically a time scale or standard) is used as the basis for keeping official civil time within a specified region or jurisdiction.
-
D.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
E.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc0742288190a594be859184841a |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.