Triple
T26552546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copán dynasty |
E671716
|
entity |
| Predicate | declineCharacterizedBy |
P160464
|
FINISHED |
| Object | population decrease at Copán |
—
|
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: population decrease at Copán | Statement: [Copán dynasty, declineCharacterizedBy, population decrease at Copán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declineCharacterizedBy Context triple: [Copán dynasty, declineCharacterizedBy, population decrease at Copán]
-
A.
declineCharacterization
Indicates that an entity rejects or refuses a particular description, label, or portrayal applied to it.
-
B.
declineCharacteristics
chosen
Indicates that certain qualities, conditions, or attributes of an entity are worsening, diminishing, or deteriorating over time.
-
C.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
D.
decliningAs
Indicates that one entity is decreasing in value, intensity, or importance relative to another over time.
-
E.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6146358b88190895d8bf017e4d66b |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:48 a.m.