Triple
T26778200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutoarjo |
E670175
|
entity |
| Predicate | roadTransportFunction |
P161230
|
FINISHED |
| Object | regional bus and minibus hub |
—
|
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: regional bus and minibus hub | Statement: [Kutoarjo, roadTransportFunction, regional bus and minibus hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTransportFunction Context triple: [Kutoarjo, roadTransportFunction, regional bus and minibus hub]
-
A.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
B.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
C.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
D.
modernTransportRoute
Indicates a transportation route that uses contemporary or up-to-date modes, infrastructure, or standards for moving people or goods between locations.
-
E.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
- F. None of above. chosen
Provenance (4 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6197855f481909d48a0fe694b8c53 |
completed | May 2, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 4:06 a.m.