Triple
T1688382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yavuz Sultan Selim Bridge |
E36493
|
entity |
| Predicate | numberOfRailTracks |
P17128
|
FINISHED |
| Object | 2 rail tracks |
—
|
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: 2 rail tracks | Statement: [Yavuz Sultan Selim Bridge, numberOfRailTracks, 2 rail tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRailTracks Context triple: [Yavuz Sultan Selim Bridge, numberOfRailTracks, 2 rail tracks]
-
A.
numberOfRailwayTracks
chosen
Indicates the quantity of railway tracks associated with or present at a given entity or location.
-
B.
numberOfRailLines
Indicates the total count of rail lines associated with or serving a given entity.
-
C.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
D.
usesRailGauge
Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
-
E.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.