Triple
T8688453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth parallels system |
E206224
|
entity |
| Predicate | angleRange |
P4679
|
FINISHED |
| Object | 0° to 90° 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: 0° to 90° north | Statement: [Earth parallels system, angleRange, 0° to 90° north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angleRange Context triple: [Earth parallels system, angleRange, 0° to 90° north]
-
A.
angleProperty
Indicates that a relationship specifies a particular geometric or quantitative characteristic (such as measure, type, or orientation) of an angle between entities.
-
B.
angleCondition
Indicates that a specified geometric relationship holds between angles, such as equality, inequality, or a particular angular constraint.
-
C.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
E.
range
chosen
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc57334b0c8190903a5a1784e74791 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.