Triple
T13689974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carme group |
E328234
|
entity |
| Predicate | hasMeanOrbitalPeriod |
P2028
|
FINISHED |
| Object | about 735 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 735 days | Statement: [Carme group, hasMeanOrbitalPeriod, about 735 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeanOrbitalPeriod Context triple: [Carme group, hasMeanOrbitalPeriod, about 735 days]
-
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.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
-
D.
orbitalPeriodRange_minutesLowerBound
Indicates the minimum value of an object's orbital period, expressed in minutes, within a specified range.
-
E.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6721c248190ac48491b5f39c8f0 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.