Triple
T32270770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransJakarta |
E824408
|
entity |
| Predicate | corridor1Route |
P173905
|
FINISHED |
| Object | Blok M – Kota |
—
|
NE NERFINISHED |
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: Blok M – Kota | Statement: [TransJakarta, corridor1Route, Blok M – Kota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corridor1Route Context triple: [TransJakarta, corridor1Route, Blok M – Kota]
-
A.
firstCorridorOpened
Indicates that the first corridor in a sequence or structure has been opened or made accessible.
-
B.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
C.
focusesOnCorridor
Indicates that an action, attention, or process is directed specifically toward a corridor or passageway.
-
D.
corridorNumber
Indicates the specific corridor identifier or number associated with a location or entity within a building or structured layout.
-
E.
corridorStartApprox
Indicates an approximate or estimated starting point of a corridor in relation to another spatial element or reference.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc8766048190a663b878529d5450 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:42 a.m.