Triple
T7107167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya civilization |
E165616
|
entity |
| Predicate | usedAgriculturalTechnique |
P4104
|
FINISHED |
| Object | terracing |
—
|
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: terracing | Statement: [Maya civilization, usedAgriculturalTechnique, terracing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAgriculturalTechnique Context triple: [Maya civilization, usedAgriculturalTechnique, terracing]
-
A.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
B.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
C.
agriculturalPractice
chosen
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
D.
usedIrrigation
Indicates that an entity applied or employed an irrigation system or method to supply water to land or crops.
-
E.
agriculturalShiftTo
Indicates a change or transition in agricultural practices, production, or land use from one type, method, or crop to another.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.