Triple
T37263104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cataby |
E924306
|
entity |
| Predicate | isRoadsideStopOn |
P107291
|
FINISHED |
| Object | route between Perth and Geraldton |
—
|
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: route between Perth and Geraldton | Statement: [Cataby, isRoadsideStopOn, route between Perth and Geraldton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRoadsideStopOn Context triple: [Cataby, isRoadsideStopOn, route between Perth and Geraldton]
-
A.
isScenicStopOn
Indicates that a location serves as a designated scenic viewpoint or attraction situated along a particular route or path.
-
B.
hasRoadsideFacility
chosen
Indicates that a location or route segment is associated with a facility or service situated along its roadside.
-
C.
isPilgrimageStopOn
Indicates that a location serves as a designated stop or waypoint along a particular pilgrimage route.
-
D.
isRoadsideCommunity
Indicates that a community is located alongside or immediately adjacent to a road or highway.
-
E.
isCoastalRoad
Indicates that a road is located along or adjacent to a coastline, typically running parallel to the sea or ocean.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.