Triple
T4184793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadi–San Francisco |
E88283
|
entity |
| Predicate | directionFromNadi |
P30236
|
FINISHED |
| Object | northeast |
—
|
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: northeast | Statement: [Nadi–San Francisco, directionFromNadi, northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromNadi Context triple: [Nadi–San Francisco, directionFromNadi, northeast]
-
A.
directionFromEarth
Indicates the compass or spatial direction in which an entity is located as observed from Earth.
-
B.
directionFromSun
Indicates the orientation or bearing of an entity as measured outward from the Sun.
-
C.
directionalDesignation
chosen
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
D.
orientationMeaning
Indicates the conceptual or semantic interpretation associated with a particular orientation or directional arrangement between entities.
-
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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.