Triple
T36251118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogwa |
E891804
|
entity |
| Predicate | locatedInDirectionWithinState |
P44650
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Ogwa, locatedInDirectionWithinState, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionWithinState Context triple: [Ogwa, locatedInDirectionWithinState, south]
-
A.
geographicDirectionWithinState
chosen
Indicates that one location lies in a specified cardinal or relative geographic direction within the boundaries of a particular state.
-
B.
regionalLocationWithinState
Indicates that one region is geographically located within the boundaries of a specific state.
-
C.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
D.
positionWithinProvince
Indicates that one entity’s location lies inside the geographic or administrative boundaries of a specified province.
-
E.
directionWithinRegion
Indicates that a specified direction or heading is located entirely inside the boundaries of a given geographic or spatial region.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.