Triple
T25596555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bojong Gede |
E641669
|
entity |
| Predicate | commuterFlowDestination |
P61070
|
FINISHED |
| Object | Bogor |
—
|
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: Bogor | Statement: [Bojong Gede, commuterFlowDestination, Bogor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterFlowDestination Context triple: [Bojong Gede, commuterFlowDestination, Bogor]
-
A.
commuterDestination
chosen
Indicates that a location serves as the endpoint or target place to which a person regularly travels for commuting.
-
B.
commuterHubFor
Indicates a location that serves as a primary transit or gathering point for commuters traveling to or from another place.
-
C.
commutesBetween
Indicates a regular pattern of travel back and forth between two locations, typically for work, study, or routine activities.
-
D.
commuterCorridorFor
Indicates a route or area that serves as a primary pathway for regular travel between two locations, typically used by commuters.
-
E.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a30ad081909c4acab2736475a1 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 4:28 p.m.