Triple
T6958294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Inscriptions |
E161302
|
entity |
| Predicate | inscriptionsContent |
P9127
|
FINISHED |
| Object | dynastic history of Palenque |
—
|
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: dynastic history of Palenque | Statement: [Temple of the Inscriptions, inscriptionsContent, dynastic history of Palenque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionsContent Context triple: [Temple of the Inscriptions, inscriptionsContent, dynastic history of Palenque]
-
A.
mainContentOfInscriptions
chosen
Indicates that something represents the primary textual or symbolic content conveyed by a set of inscriptions.
-
B.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
C.
scriptOfInscription
Indicates the writing system or script in which a given inscription is written.
-
D.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
E.
inscriptionsFoundAt
Indicates that inscriptions are discovered or located at a particular place or site.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dad240ac8190808014a5b4920b41 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.