Triple
T26691201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lions Den |
E672885
|
entity |
| Predicate | roadsideFunction |
P161606
|
FINISHED |
| Object | local produce sales point |
—
|
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: local produce sales point | Statement: [Lions Den, roadsideFunction, local produce sales point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadsideFunction Context triple: [Lions Den, roadsideFunction, local produce sales point]
-
A.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
-
B.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
-
E.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61ad613608190855de13501a86007 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f61a16b7848190bf20d2be7e5a16c1 |
completed | May 2, 2026, 3:36 p.m. |
Created at: April 27, 2026, 3:26 a.m.