Triple
T34177293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 1 (Almaty Metro) |
E876707
|
entity |
| Predicate | isInauguralLineOf |
P172419
|
FINISHED |
| Object | Almaty Metro |
—
|
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: Almaty Metro | Statement: [Line 1 (Almaty Metro), isInauguralLineOf, Almaty Metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInauguralLineOf Context triple: [Line 1 (Almaty Metro), isInauguralLineOf, Almaty Metro]
-
A.
inauguralLineOf
chosen
Indicates that one entity is the first line or route to begin operation within a particular system, service, or network.
-
B.
isInauguralElectionFor
Indicates that an election is the first (inaugural) occurrence held for a particular office, position, or governing body.
-
C.
inauguratedWith
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
-
D.
isInauguralGameOf
Indicates that one game is the first-ever or opening game associated with a particular event, season, team, or competition.
-
E.
inauguralRouteOf
Indicates that a particular route was used as the inaugural or first official route for a given service, vehicle, or operation.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7100252d081908f2007bf671eabad |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.