Triple
T5201984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SagDEG |
E117412
|
entity |
| Predicate | hasOrbitalPeriod_approx |
P2028
|
FINISHED |
| Object | ~0.8–1.0 billion years |
—
|
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: ~0.8–1.0 billion years | Statement: [SagDEG, hasOrbitalPeriod_approx, ~0.8–1.0 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalPeriod_approx Context triple: [SagDEG, hasOrbitalPeriod_approx, ~0.8–1.0 billion years]
-
A.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
C.
minimumOrbitIntersectionDistanceWithEarth_au
Indicates the smallest distance, measured in astronomical units, between an object's orbit and Earth's orbit at their closest point of approach.
-
D.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
E.
timeInOrbit_days
Indicates the number of days an object has spent in orbit around a celestial body.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.