Triple
T33285000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North |
E852157
|
entity |
| Predicate | usedAsZeroPointFor |
P65427
|
FINISHED |
| Object | compass bearings |
—
|
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: compass bearings | Statement: [North, usedAsZeroPointFor, compass bearings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsZeroPointFor Context triple: [North, usedAsZeroPointFor, compass bearings]
-
A.
usesBasePoint
Indicates that one entity performs an operation or defines a structure by referencing or relying on a specific base point.
-
B.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
C.
formsZeroPointFor
chosen
Indicates that one entity serves as the reference or origin point (zero point) for measuring or defining another entity.
-
D.
isUsedAsReferencePointInNightSky
Indicates that something serves as a positional or navigational reference point when observing or orienting in the night sky.
-
E.
hasZeroPosition
Indicates that an entity occupies or is assigned to the reference (zero) position within a defined coordinate system or ordered structure.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 1:32 a.m.