Triple
T25119942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purépecha pantheon |
E629237
|
entity |
| Predicate | primaryMoonDeity |
P7648
|
FINISHED |
| Object | Xaratanga |
—
|
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: Xaratanga | Statement: [Purépecha pantheon, primaryMoonDeity, Xaratanga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMoonDeity Context triple: [Purépecha pantheon, primaryMoonDeity, Xaratanga]
-
A.
associatedMoon
Indicates that one celestial body is the moon that is associated with, or orbits, another celestial body.
-
B.
moonSightingRole
Indicates the specific role or capacity an entity has in the context of observing, reporting, or validating a moon sighting.
-
C.
majorUranianMoon
Indicates that the subject is one of the primary large moons orbiting the planet Uranus.
-
D.
areFirstDiscoveredMoonsOf
Indicates that the related entities are moons that were the first ones discovered orbiting a particular celestial body.
-
E.
mainDeity
chosen
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 18, 2026, 6:27 a.m.