Triple
T23947622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classical Maya language |
E602955
|
entity |
| Predicate | primaryEvidence |
P2296
|
FINISHED |
| Object | inscriptions on monuments |
—
|
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: inscriptions on monuments | Statement: [Classical Maya language, primaryEvidence, inscriptions on monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEvidence Context triple: [Classical Maya language, primaryEvidence, inscriptions on monuments]
-
A.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
B.
primarySources
chosen
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
C.
primaryElement
Indicates that one element is the main or most important component within a set, structure, or context relative to other associated elements.
-
D.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
E.
primaryCase
Indicates that an entity is the main or leading instance in a set of related cases or occurrences.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02fb4fc8190835baf3bcf909d4d |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:18 p.m.