Triple
T5535790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechta |
E145157
|
entity |
| Predicate | finalOrbitType |
P7214
|
FINISHED |
| Object | heliocentric 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: heliocentric orbit | Statement: [Mechta, finalOrbitType, heliocentric orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalOrbitType Context triple: [Mechta, finalOrbitType, heliocentric orbit]
-
A.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
C.
hasOrbitalDirection
Indicates that one celestial body orbits another in a specified directional sense (e.g., prograde or retrograde).
-
D.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
E.
orbitalBodyType
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01faed1d08190b6a57faedaf1b56a |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.