Triple
T33062810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panagsama Beach |
E846016
|
entity |
| Predicate | approximateTravelTimeFrom |
P53938
|
FINISHED |
| Object | Cebu City |
—
|
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: Cebu City | Statement: [Panagsama Beach, approximateTravelTimeFrom, Cebu City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateTravelTimeFrom Context triple: [Panagsama Beach, approximateTravelTimeFrom, Cebu City]
-
A.
approximateTripDuration
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
-
B.
hasApproximateWalkingTimeTo
chosen
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
C.
approximateDrivingTime
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
-
D.
reducedTravelTimeFrom
Indicates that one entity has caused or experienced a decrease in the amount of time required to travel from a specified origin entity.
-
E.
travelTimeAdvantage
Indicates that one option provides a shorter or more favorable travel time compared to another.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.