Triple
T10309069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totonac languages |
E241837
|
entity |
| Predicate | historicalDepth |
P28626
|
FINISHED |
| Object | pre-Columbian |
—
|
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: pre-Columbian | Statement: [Totonac languages, historicalDepth, pre-Columbian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDepth Context triple: [Totonac languages, historicalDepth, pre-Columbian]
-
A.
historicalLevel
chosen
Indicates the degree or extent to which something is related to, situated in, or characterized by a particular historical period or context.
-
B.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
C.
historicalVolume
Indicates a relationship where a volume (such as a book, record, or dataset) pertains to or documents historical information or events.
-
D.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
E.
historicalValue
Indicates that something possesses significance, importance, or relevance due to its connection with past events, periods, or developments.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:47 a.m.