Triple
T24064733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PR-1 |
E596056
|
entity |
| Predicate | directionNorth |
P103584
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [PR-1, directionNorth, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionNorth Context triple: [PR-1, directionNorth, north]
-
A.
northernDirection
chosen
Indicates a spatial relationship where one entity is located to the north of another entity.
-
B.
directionInNorthernHemisphere
Indicates that the specified direction is defined or measured relative to the orientation of the Northern Hemisphere (e.g., based on its geographic or celestial reference frame).
-
C.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
D.
latitudeDirection
Indicates the cardinal direction (north or south) associated with a given latitude value relative to the equator.
-
E.
northSouthAxis
Indicates a spatial or directional relationship aligned along the north–south axis between entities.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5aa1a48190afec72bbcfd379c3 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:39 p.m.