Triple
T34949643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madura |
E1007953
|
entity |
| Predicate | hasRoadhouse |
P197034
|
FINISHED |
| Object | Madura Roadhouse |
—
|
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: Madura Roadhouse | Statement: [Madura, hasRoadhouse, Madura Roadhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadhouse Context triple: [Madura, hasRoadhouse, Madura Roadhouse]
-
A.
roadhouseProvides
Indicates that a roadhouse supplies or makes available a particular good, service, or amenity.
-
B.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: May 3, 2026, 4 p.m.