Triple
T10286653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gillikin Country |
E241244
|
entity |
| Predicate | hasCompassPosition |
P54717
|
FINISHED |
| Object | northern quadrant of Oz |
—
|
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: northern quadrant of Oz | Statement: [Gillikin Country, hasCompassPosition, northern quadrant of Oz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompassPosition Context triple: [Gillikin Country, hasCompassPosition, northern quadrant of Oz]
-
A.
hasMagneticHeading
chosen
Indicates the directional orientation of an entity relative to magnetic north, typically expressed as a magnetic compass bearing.
-
B.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
C.
hasQiblaDirection
Indicates the directional relationship specifying which way one should face (toward the Kaaba in Mecca) for prayer.
-
D.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
E.
hasCanonicalPosition
Indicates that an entity occupies a standard, officially recognized, or authoritative position or location within a defined structure or system.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:40 a.m.