Triple
T34146023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Chalco |
E875856
|
entity |
| Predicate | primaryUsePreHispanic |
P37102
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Lake Chalco, primaryUsePreHispanic, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUsePreHispanic Context triple: [Lake Chalco, primaryUsePreHispanic, agriculture]
-
A.
preColumbianUse
Indicates that something was used or utilized during the period before European (Columbian) contact with the Americas.
-
B.
isPreColumbian
Indicates that something existed, occurred, or was created in the Americas before the arrival of Christopher Columbus in 1492.
-
C.
preColumbianFunction
Indicates that something served a particular role or purpose during the pre-Columbian period, before European contact with the Americas.
-
D.
preHispanicUse
chosen
Indicates that something was used or practiced during the pre-Hispanic period, before Spanish contact or colonization.
-
E.
preHispanic
Indicates that something existed in, originated from, or is associated with the period before Hispanic or Spanish influence or colonization.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.