Triple
T22998932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ecliptic Pole |
E572582
|
entity |
| Predicate | isFixedRelativeTo |
P42535
|
FINISHED |
| Object | ecliptic plane |
—
|
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: ecliptic plane | Statement: [North Ecliptic Pole, isFixedRelativeTo, ecliptic plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFixedRelativeTo Context triple: [North Ecliptic Pole, isFixedRelativeTo, ecliptic plane]
-
A.
isFixedLink
Indicates that there is a permanent, non-movable connection or linkage established between two entities.
-
B.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
C.
isFixedFieldOf
Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
-
D.
positionedRelativeTo
chosen
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
E.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f54ce88190930530958e2a1830 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.