Triple
T14907855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poniente |
E371181
|
entity |
| Predicate | hasOppositeDirectionTo |
P116628
|
FINISHED |
| Object | Levante |
—
|
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: Levante | Statement: [Poniente, hasOppositeDirectionTo, Levante]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppositeDirectionTo Context triple: [Poniente, hasOppositeDirectionTo, Levante]
-
A.
hasOppositeTime
Indicates a temporal relationship where one time point or period is positioned as the direct opposite or inverse of another within a defined temporal framework (e.g., day vs. night, past vs. future).
-
B.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
C.
hasOppositeStatus
Indicates that two entities hold directly contrasting or mutually exclusive statuses within a given context.
-
D.
hasOppositeStructure
Indicates that one entity possesses a structure that is the inverse or opposite in form, arrangement, or organization relative to another entity.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61b3c808190b4f6df4e5cb401ad |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:23 a.m.