Triple
T35629815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid belt |
E1029552
|
entity |
| Predicate | locatedBetweenOrbitOf |
P207072
|
FINISHED |
| Object | Mars |
E20154
|
NE 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: Mars | Statement: [Asteroid belt, locatedBetweenOrbitOf, Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedBetweenOrbitOf Context triple: [Asteroid belt, locatedBetweenOrbitOf, Mars]
-
A.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
B.
isOrbitalAround
Indicates that one entity moves in a stable, curved path (orbit) around another entity due to gravitational or similar central forces.
-
C.
orbitsNear
Indicates that one object travels around another along a path that remains relatively close in spatial proximity.
-
D.
includesOrbitOf
Indicates that one entity’s orbital path or region fully contains or encompasses the orbital path or region of another entity.
-
E.
hasOrbit
Indicates that one entity follows a curved, typically gravitationally bound path around another entity.
- F. None of above. chosen
Provenance (5 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38684ee5d88190a8d0fd33fd0f8681 |
completed | June 21, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.