Triple
T19489645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 5 |
E487612
|
entity |
| Predicate | orbitsCompletedAroundSun |
P50723
|
FINISHED |
| Object | multiple heliocentric orbits |
—
|
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: multiple heliocentric orbits | Statement: [Mariner 5, orbitsCompletedAroundSun, multiple heliocentric orbits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsCompletedAroundSun Context triple: [Mariner 5, orbitsCompletedAroundSun, multiple heliocentric orbits]
-
A.
orbitsCovered
chosen
Indicates that one entity completes or spans a specified number of orbital revolutions around another entity.
-
B.
orbitsCompletedAroundMars
Indicates the number of full orbital revolutions an object has completed around Mars.
-
C.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
D.
orbitsUsed
Indicates that one entity utilizes or traverses specific orbital paths associated with another entity.
-
E.
totalOrbits
Indicates the total number of orbital paths or revolutions one entity completes around another within a defined system or timeframe.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348ad4088190b530f47efca90165 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.