Triple
T34949632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundrabilla |
E1007952
|
entity |
| Predicate | roadUserTypeServed |
P181882
|
FINISHED |
| Object | tourists |
—
|
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: tourists | Statement: [Mundrabilla, roadUserTypeServed, tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadUserTypeServed Context triple: [Mundrabilla, roadUserTypeServed, tourists]
-
A.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
B.
rightOfWayUsedFor
Indicates that a particular right of way is utilized for a specific purpose, activity, or type of use.
-
C.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
D.
typeOfRoadOperated
Indicates that an entity operates or manages a specific type or category of road.
-
E.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cf61948190b98185d961609554 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782c848fc8190baea8c845ca9079f |
completed | May 3, 2026, 5:15 p.m. |
Created at: May 3, 2026, 4 p.m.