Triple
T36930578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya astronomy |
E913468
|
entity |
| Predicate | observedBody |
P74941
|
FINISHED |
| Object | Sun |
—
|
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: Sun | Statement: [Maya astronomy, observedBody, Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedBody Context triple: [Maya astronomy, observedBody, Sun]
-
A.
observedAstronomicalBody
chosen
Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
-
B.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
C.
observedAstronomicalEvent
Indicates that an entity has witnessed, detected, or recorded a specific astronomical event.
-
D.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
E.
inSolarSystemBody
Indicates that one entity is located within, on, or as part of a specified solar system body (such as a planet, moon, or asteroid).
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.