Triple
T12861537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İZULAŞ |
E307601
|
entity |
| Predicate | transportationNetworkType |
P23132
|
FINISHED |
| Object | bus network |
—
|
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: bus network | Statement: [İZULAŞ, transportationNetworkType, bus network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationNetworkType Context triple: [İZULAŞ, transportationNetworkType, bus network]
-
A.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
B.
typeOfTransportInfrastructure
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
C.
trailNetworkType
Indicates the classification of a trail within a broader trail network, such as its role, category, or type of route in that system.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
routeNetworkType
chosen
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.