Triple
T21884570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 25930 |
E540371
|
entity |
| Predicate | orbitalPeriodOfEclipsingPair |
P2028
|
FINISHED |
| Object | about 5.73 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 5.73 days | Statement: [HIP 25930, orbitalPeriodOfEclipsingPair, about 5.73 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalPeriodOfEclipsingPair Context triple: [HIP 25930, orbitalPeriodOfEclipsingPair, about 5.73 days]
-
A.
isEclipsingBinary
Indicates that two stars form a binary system whose orbital plane is aligned so that, from the observer’s viewpoint, one periodically passes in front of the other, causing observable eclipses in brightness.
-
B.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
-
D.
epochOfOrbit
Indicates the specific reference time at which an orbit’s parameters are defined or measured.
-
E.
orbitalPeriodRange_minutesLowerBound
Indicates the minimum value of an object's orbital period, expressed in minutes, within a specified range.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.