Triple
T19927301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varketili |
E478957
|
entity |
| Predicate | directionTerminusFor |
P34413
|
FINISHED |
| Object | south-eastern direction of Akhmeteli–Varketili Line |
—
|
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: south-eastern direction of Akhmeteli–Varketili Line | Statement: [Varketili, directionTerminusFor, south-eastern direction of Akhmeteli–Varketili Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionTerminusFor Context triple: [Varketili, directionTerminusFor, south-eastern direction of Akhmeteli–Varketili Line]
-
A.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
-
B.
terminusDirection
chosen
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
C.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
D.
transportTerminusFor
Indicates that a location serves as the endpoint or final stop for a particular transport route or service.
-
E.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659ca52c881908dc8053bf61be4c4 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.