Triple
T24815458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec codices |
E620907
|
entity |
| Predicate | postConquestFeature |
P46175
|
FINISHED |
| Object | alphabetic annotations |
—
|
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: alphabetic annotations | Statement: [Aztec codices, postConquestFeature, alphabetic annotations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postConquestFeature Context triple: [Aztec codices, postConquestFeature, alphabetic annotations]
-
A.
postConquestUse
Indicates how something is used, occupied, or functionally repurposed after a conquest has taken place.
-
B.
afterConquest
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
C.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
D.
afterConquestName
Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
-
E.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:02 a.m.