Triple
T33829667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 107556 |
E867061
|
entity |
| Predicate | orbitalPeriodInnerBinary |
P2028
|
FINISHED |
| Object | about 1.02 days |
—
|
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 1.02 days | Statement: [HIP 107556, orbitalPeriodInnerBinary, about 1.02 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalPeriodInnerBinary Context triple: [HIP 107556, orbitalPeriodInnerBinary, about 1.02 days]
-
A.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
-
C.
orbitalPeriodRange_minutesLowerBound
Indicates the minimum value of an object's orbital period, expressed in minutes, within a specified range.
-
D.
averageOrbitalPeriodRange
Indicates the range of values within which the average orbital period of an object or system falls.
-
E.
orbitsInteriorTo
Indicates that one object orbits another along a path that lies entirely within the orbital path of a third, outer reference object.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.