Triple
T24910368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Canyon (Cukang Taneuh) |
E623827
|
entity |
| Predicate | distanceFromPangandaran |
P161625
|
FINISHED |
| Object | approximately 30 kilometers |
—
|
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 30 kilometers | Statement: [Green Canyon (Cukang Taneuh), distanceFromPangandaran, approximately 30 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPangandaran Context triple: [Green Canyon (Cukang Taneuh), distanceFromPangandaran, approximately 30 kilometers]
-
A.
approxDistanceFromPangandaran
chosen
Indicates that one entity is located at an approximate distance from the reference location Pangandaran.
-
B.
approxTravelTimeFromPangandaran
Indicates an estimated duration required to travel from Pangandaran to another location.
-
C.
distanceToPrambanan
Indicates the spatial distance between an entity and the location of Prambanan.
-
D.
distanceFromKundapura
Indicates the measured spatial distance between a given entity and the location of Kundapura.
-
E.
distanceFromDenpasar
Indicates the spatial distance between a given location and Denpasar.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 5:27 a.m.