Triple
T22998918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ecliptic Pole |
E572582
|
entity |
| Predicate | isPerpendicularTo |
P2055
|
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, isPerpendicularTo, ecliptic plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerpendicularTo Context triple: [North Ecliptic Pole, isPerpendicularTo, ecliptic plane]
-
A.
perpendicularTo
chosen
Indicates that one entity is oriented at a right angle (90 degrees) to another entity.
-
B.
isParallelWithRespectTo
Indicates that two or more entities maintain a constant separation and never intersect within a specified reference or coordinate system.
-
C.
isParallelBodyTo
Indicates that one body or object is oriented such that its main axis or surface is parallel to that of another body or object.
-
D.
orientedParallelTo
Indicates that one entity is parallel to another with a specified or consistent direction or orientation.
-
E.
isOnSlopeOf
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or 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_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.