Triple
T13180172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 90482 Orcus |
E313700
|
entity |
| Predicate | hasOrbitalPeriodYears |
P9857
|
FINISHED |
| Object | 247 |
—
|
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: 247 | Statement: [90482 Orcus, hasOrbitalPeriodYears, 247]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalPeriodYears Context triple: [90482 Orcus, hasOrbitalPeriodYears, 247]
-
A.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
timeInOrbit_days
Indicates the number of days an object has spent in orbit around a celestial body.
-
C.
hasAverageYearLength
chosen
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
D.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
E.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.