Triple
T26014122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muisca lunisolar calendar |
E646978
|
entity |
| Predicate | agriculturalFunction |
P15634
|
FINISHED |
| Object | sowing schedules |
—
|
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: sowing schedules | Statement: [Muisca lunisolar calendar, agriculturalFunction, sowing schedules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agriculturalFunction Context triple: [Muisca lunisolar calendar, agriculturalFunction, sowing schedules]
-
A.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
B.
agriculturalRole
chosen
Indicates a role or function that an entity has within agricultural activities, production, or systems.
-
C.
agriculturalFocus
Indicates that an entity is primarily concerned with, oriented toward, or specializing in agriculture or farming-related activities.
-
D.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
E.
agriculturalPractice
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b7eb6881909e1768f5f856be32 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:03 a.m.