Triple
T16200431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amor group |
E393182
|
entity |
| Predicate | hasTypicalSemiMajorAxis |
P9971
|
FINISHED |
| Object | greater than 1 AU |
—
|
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: greater than 1 AU | Statement: [Amor group, hasTypicalSemiMajorAxis, greater than 1 AU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSemiMajorAxis Context triple: [Amor group, hasTypicalSemiMajorAxis, greater than 1 AU]
-
A.
semiMajorAxis
chosen
Indicates the length of the longest radius of an elliptical orbit, measuring the average distance between the orbiting body and the central body.
-
B.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
D.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
E.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22709b0d88190b40787e0520d02ab |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.