Triple
T37105267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1862 Apollo |
E918822
|
entity |
| Predicate | hasOrbitalNode |
P17317
|
FINISHED |
| Object | inside Earth’s orbit |
—
|
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: inside Earth’s orbit | Statement: [1862 Apollo, hasOrbitalNode, inside Earth’s orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalNode Context triple: [1862 Apollo, hasOrbitalNode, inside Earth’s orbit]
-
A.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
B.
isOrbitalTo
Indicates that one entity moves in a curved, repeating path around another entity under the influence of a central force, typically gravity.
-
C.
hasOrbit
Indicates that one entity follows a curved, typically gravitationally bound path around another entity.
-
D.
hasOrbitalOrientation
Indicates that one entity has a specific spatial or directional orientation in its orbit relative to another reference frame or object.
-
E.
hasOrbitalRegion
chosen
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:14 p.m.