Triple
T35665855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medium Earth orbit |
E1030560
|
entity |
| Predicate | typicalNavigationOrbitPeriod_hours |
P183591
|
FINISHED |
| Object | about 12 |
—
|
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 12 | Statement: [Medium Earth orbit, typicalNavigationOrbitPeriod_hours, about 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNavigationOrbitPeriod_hours Context triple: [Medium Earth orbit, typicalNavigationOrbitPeriod_hours, about 12]
-
A.
orbitalPeriodRange_hours
chosen
Indicates the range of time, measured in hours, that an object takes to complete one full orbit around another body.
-
B.
orbitalPeriodUnit
Indicates the unit of measurement used to express an object's orbital period.
-
C.
timeInOrbit_days
Indicates the number of days an object has spent in orbit around a celestial body.
-
D.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
E.
orbitalPeriodRange_minutesUpperBound
Indicates the maximum value, in minutes, of the allowed or observed range for an entity’s orbital period.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.