Triple
T24027183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabo de San Antonio |
E594995
|
entity |
| Predicate | extremePointDirection |
P47428
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Cabo de San Antonio, extremePointDirection, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extremePointDirection Context triple: [Cabo de San Antonio, extremePointDirection, west]
-
A.
directionalExtreme
chosen
Indicates that one entity lies at or near the furthest extent or boundary in a specified direction relative to another entity.
-
B.
hasExtremePoint
Indicates that one entity possesses or includes another entity that is an extreme (e.g., maximum or minimum) point within its structure or boundary.
-
C.
peakDirectionExpress
Indicates the direction in which a peak (such as a maximum value or intensity) is oriented or expressed.
-
D.
directionalExtent
Indicates the directional span or reach of something from a reference point, specifying how far it extends along a particular direction.
-
E.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76c083c819090784ecb42effbae |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.