Triple
T22162674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coral Beach (Claigan Coral Beach) |
E547709
|
entity |
| Predicate | hasApproxWalkingTimeFromCarPark |
P53938
|
FINISHED |
| Object | 20–30 minutes |
—
|
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: 20–30 minutes | Statement: [Coral Beach (Claigan Coral Beach), hasApproxWalkingTimeFromCarPark, 20–30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproxWalkingTimeFromCarPark Context triple: [Coral Beach (Claigan Coral Beach), hasApproxWalkingTimeFromCarPark, 20–30 minutes]
-
A.
hasApproximateWalkingTimeTo
chosen
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
B.
hasParkingNearby
Indicates that a location has one or more parking facilities or spaces available within a close surrounding area.
-
C.
hasNearbyParkEntrance
Indicates that one location is situated close to an entrance of a park.
-
D.
approximateTripDuration
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
-
E.
approximateDrivingTime
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2e47a88190a3b5c05398605f68 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.