Triple
T22999052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polaris |
E572584
|
entity |
| Predicate | orbitalPeriod_PolarisA-B_years |
P2028
|
FINISHED |
| Object | about 26,000 |
—
|
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: about 26,000 | Statement: [Polaris, orbitalPeriod_PolarisA-B_years, about 26,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalPeriod_PolarisA-B_years Context triple: [Polaris, orbitalPeriod_PolarisA-B_years, about 26,000]
-
A.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
-
C.
meanOrbitalRadius_km
Indicates the average distance, measured in kilometers, between an orbiting body and the center of the object it orbits.
-
D.
planetOrbitalDistance
Indicates the average distance between a planet and the celestial body it orbits, typically measured along its orbital path.
-
E.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
- 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.