Triple
T25745553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inner Solar System |
E648335
|
entity |
| Predicate | containsOrbitalRegion |
P17317
|
FINISHED |
| Object | near-Earth object region |
—
|
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: near-Earth object region | Statement: [inner Solar System, containsOrbitalRegion, near-Earth object region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsOrbitalRegion Context triple: [inner Solar System, containsOrbitalRegion, near-Earth object region]
-
A.
hasOrbitalRegion
chosen
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
B.
includesOrbitOf
Indicates that one entity’s orbital path or region fully contains or encompasses the orbital path or region of another entity.
-
C.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
hasOrbitalSignature
Indicates that one entity possesses or is characterized by a distinctive orbital pattern or trajectory associated with another entity.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 3:51 a.m.