Triple
T19179860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarke orbit |
E469541
|
entity |
| Predicate | typicalLongitudeRange |
P23540
|
FINISHED |
| Object | 0 to 360 degrees along equator |
—
|
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 360 degrees along equator | Statement: [Clarke orbit, typicalLongitudeRange, 0 to 360 degrees along equator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLongitudeRange Context triple: [Clarke orbit, typicalLongitudeRange, 0 to 360 degrees along equator]
-
A.
regionLongitudeRange
chosen
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
typicalCityLongitude
Indicates the standard or representative longitude value associated with a given city.
-
C.
intendedLongitude
Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
-
D.
eclipticLongitudeRange
Indicates that an entity’s ecliptic longitude lies within a specified angular range along the ecliptic.
-
E.
latitudeRangeApproximate
Indicates that the latitude of an entity falls within an approximate or loosely bounded range, rather than an exact or strictly defined interval.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61ae4108190b3715261cac2dd86 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.