Triple
T25504814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatolian Railway Company |
E639218
|
entity |
| Predicate | peakNetworkLength |
P18592
|
FINISHED |
| Object | approximately 1,000 km |
—
|
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: approximately 1,000 km | Statement: [Anatolian Railway Company, peakNetworkLength, approximately 1,000 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakNetworkLength Context triple: [Anatolian Railway Company, peakNetworkLength, approximately 1,000 km]
-
A.
networkLength
chosen
Indicates the total measured extent or distance covered by a network (e.g., of connections, links, or paths).
-
B.
networkDepth
Indicates the hierarchical level or number of intermediary layers between connected elements within a network structure.
-
C.
networkLengthContext
Indicates the contextual conditions or parameters under which a network’s length is defined, measured, or interpreted.
-
D.
networkNumberSize
Indicates the size or magnitude associated with a network’s identifying number or address range.
-
E.
pathLength
Indicates the measured distance or length of a path connecting two points or locations.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f804c9f48190be4e560a60ee6242 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:46 p.m.