Triple
T33887908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Becán |
E868678
|
entity |
| Predicate | approximateAbandonment |
P176127
|
FINISHED |
| Object | Terminal Classic period |
—
|
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: Terminal Classic period | Statement: [Becán, approximateAbandonment, Terminal Classic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAbandonment Context triple: [Becán, approximateAbandonment, Terminal Classic period]
-
A.
abandonedApprox
chosen
Indicates that an entity ceased to maintain, use, or care for another entity at approximately a given time or under roughly specified circumstances.
-
B.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
C.
periodOfAbandonment
Indicates a time span during which something is left unused, unattended, or not maintained.
-
D.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
E.
partiallyAbandoned
Indicates that an entity has been abandoned to some extent, but still retains partial use, occupancy, or maintenance.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:48 a.m.