Triple
T25750255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 433 Eros |
E648452
|
entity |
| Predicate | firstOrbitedBy |
P11957
|
FINISHED |
| Object | NEAR Shoemaker |
—
|
NE NERFINISHED |
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 Shoemaker | Statement: [433 Eros, firstOrbitedBy, NEAR Shoemaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOrbitedBy Context triple: [433 Eros, firstOrbitedBy, NEAR Shoemaker]
-
A.
orbitedBody
chosen
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
B.
isLagrangianSatelliteOf
Indicates that one celestial body occupies a Lagrangian point and thus functions as a gravitationally bound satellite associated with another primary body.
-
C.
isOrbitalAround
Indicates that one entity moves in a stable, curved path (orbit) around another entity due to gravitational or similar central forces.
-
D.
hasOrbitalRelationship
Indicates that one entity is in an orbital relationship with another, such as revolving around or being gravitationally bound in a regular orbit.
-
E.
hasOrbit
Indicates that one entity follows a curved, typically gravitationally bound path around 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 22, 2026, 4:33 a.m.