Triple
T23828823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth's Cry Heaven's Smile |
E589457
|
entity |
| Predicate | setInCelestialBody |
P32349
|
FINISHED |
| Object | Europa |
—
|
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: Europa | Statement: [Earth's Cry Heaven's Smile, setInCelestialBody, Europa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInCelestialBody Context triple: [Earth's Cry Heaven's Smile, setInCelestialBody, Europa]
-
A.
associatedWithCelestialBody
Indicates a relationship in which an entity has a connection, link, or relevance to a specific celestial body (such as a planet, star, or moon).
-
B.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
C.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
D.
inSolarSystemBody
chosen
Indicates that one entity is located within, on, or as part of a specified solar system body (such as a planet, moon, or asteroid).
-
E.
collectedOnCelestialBody
Indicates that something (typically a sample or data) was gathered or obtained while located on a specific celestial body.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f304f08190bd965df06f013b3f |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8 p.m.