Triple
T24910417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batu Karas Beach |
E623828
|
entity |
| Predicate | approxTravelTimeFromPangandaran |
P162068
|
FINISHED |
| Object | about 45–60 minutes by road |
—
|
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: about 45–60 minutes by road | Statement: [Batu Karas Beach, approxTravelTimeFromPangandaran, about 45–60 minutes by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxTravelTimeFromPangandaran Context triple: [Batu Karas Beach, approxTravelTimeFromPangandaran, about 45–60 minutes by road]
-
A.
approxDistanceFromPangandaran
Indicates that one entity is located at an approximate distance from the reference location Pangandaran.
-
B.
travelTimeFromJakartaByCar
Indicates the amount of time it takes to travel by car from Jakarta to a specified destination.
-
C.
distanceToMataram
Indicates the measured spatial distance between a given entity’s location and the location of Mataram.
-
D.
distanceFromDenpasar
Indicates the spatial distance between a given location and Denpasar.
-
E.
distanceToPrambanan
Indicates the spatial distance between an entity and the location of Prambanan.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 18, 2026, 5:27 a.m.