Triple
T4526422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadi–Auckland |
E106188
|
entity |
| Predicate | typicalDirectionFromOrigin |
P40031
|
FINISHED |
| Object | southwest |
—
|
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: southwest | Statement: [Nadi–Auckland, typicalDirectionFromOrigin, southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDirectionFromOrigin Context triple: [Nadi–Auckland, typicalDirectionFromOrigin, southwest]
-
A.
approximateDirection
chosen
Indicates that one entity is located in a general or rough directional relation (e.g., roughly north, south, etc.) relative to another entity, without specifying an exact bearing.
-
B.
definesDirection
Indicates that one entity specifies or establishes the orientation, course, or path along which another entity is directed or proceeds.
-
C.
directionFromEarth
Indicates the compass or spatial direction in which an entity is located as observed from Earth.
-
D.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57760f4481908f69ce82be63d7f8 |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.