Triple
T36452796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1948 Kampala |
E898064
|
entity |
| Predicate | isInOrbitalRegion |
P17317
|
FINISHED |
| Object | between Mars and Jupiter |
—
|
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: between Mars and Jupiter | Statement: [1948 Kampala, isInOrbitalRegion, between Mars and Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInOrbitalRegion Context triple: [1948 Kampala, isInOrbitalRegion, between Mars and Jupiter]
-
A.
hasOrbitalRegion
chosen
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
B.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
C.
isOrbitalTo
Indicates that one entity moves in a curved, repeating path around another entity under the influence of a central force, typically gravity.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
isOrbitalAround
Indicates that one entity moves in a stable, curved path (orbit) around another entity due to gravitational or similar central forces.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.