Triple
T17048383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uaxactún |
E413628
|
entity |
| Predicate | astronomicalFunction |
P63727
|
FINISHED |
| Object | solar observations |
—
|
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: solar observations | Statement: [Uaxactún, astronomicalFunction, solar observations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronomicalFunction Context triple: [Uaxactún, astronomicalFunction, solar observations]
-
A.
astronomicalBasis
Indicates that one entity serves as the astronomical foundation, reference, or underlying celestial cause for another entity or phenomenon.
-
B.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
C.
celestialRepresentation
Indicates that one entity serves as a symbolic or visual depiction of another entity in a celestial or astronomical context.
-
D.
astronomicalType
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
E.
astronomicalUsage
chosen
Indicates that something is used for, or serves a function within, astronomical observation, measurement, or research.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa092f08190a9e37404a9de662c |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.