Triple
T35880966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaya–Kiul line |
E1037504
|
entity |
| Predicate | junctionTypeAtTermini |
P126509
|
FINISHED |
| Object | important railway junctions |
—
|
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: important railway junctions | Statement: [Gaya–Kiul line, junctionTypeAtTermini, important railway junctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: junctionTypeAtTermini Context triple: [Gaya–Kiul line, junctionTypeAtTermini, important railway junctions]
-
A.
junctionType
chosen
Indicates the specific kind or configuration of a junction that relates connected elements or paths.
-
B.
terminusJunction
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
-
C.
isJunction
Indicates that an entity functions as a junction point where multiple paths, lines, or connections meet or intersect.
-
D.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
E.
junctionNumber
Indicates the identifying number assigned to a specific junction or intersection within a network or 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.