Triple
T18771801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | o Persei |
E459031
|
entity |
| Predicate | binaryOrbitalEccentricity |
P20350
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [o Persei, binaryOrbitalEccentricity, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binaryOrbitalEccentricity Context triple: [o Persei, binaryOrbitalEccentricity, low]
-
A.
orbitalEccentricity
chosen
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
B.
orbitsBarycenterOf
Indicates that one object follows an orbital path around the shared center of mass (barycenter) of another system or group of objects.
-
C.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
D.
obliquityOfOrbit
Indicates the angle between an object's orbital plane and a reference plane, describing how tilted the orbit is relative to that reference.
-
E.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.