Triple
T26228491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megamendung |
E655963
|
entity |
| Predicate | distanceToBogor |
P195343
|
FINISHED |
| Object | approximately 15–20 kilometers southeast of Bogor city |
—
|
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: approximately 15–20 kilometers southeast of Bogor city | Statement: [Megamendung, distanceToBogor, approximately 15–20 kilometers southeast of Bogor city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBogor Context triple: [Megamendung, distanceToBogor, approximately 15–20 kilometers southeast of Bogor city]
-
A.
distanceToBandung
Indicates the spatial distance between a given location or entity and the city of Bandung.
-
B.
distanceToJakarta_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Jakarta.
-
C.
distanceFromDenpasar
Indicates the spatial distance between a given location and Denpasar.
-
D.
distanceToMataram
Indicates the measured spatial distance between a given entity’s location and the location of Mataram.
-
E.
distanceToSamarinda_km
Indicates the physical distance, measured in kilometers, between a given location and Samarinda.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: April 26, 2026, 8:59 p.m.