Triple
T34715564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arsi |
E1000762
|
entity |
| Predicate | cropSystem |
P36685
|
FINISHED |
| Object | highland cereal cultivation |
—
|
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: highland cereal cultivation | Statement: [Arsi, cropSystem, highland cereal cultivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cropSystem Context triple: [Arsi, cropSystem, highland cereal cultivation]
-
A.
crop
Indicates the action of cutting or trimming part of an object or image, typically to remove unwanted outer areas while keeping a selected region.
-
B.
farmSystemOf
chosen
Indicates that one entity is the agricultural or farming system to which another entity belongs or with which it is associated.
-
C.
hasCropSpecies
Indicates that a particular location, field, or agricultural system is associated with or used to cultivate a specified crop species.
-
D.
servesAsFarmSystemFor
Indicates that one entity functions as a developmental or feeder system that supplies trained or prepared resources (such as players, talent, or products) to another entity.
-
E.
numberOfCrops
Indicates the quantity or count of crops associated with a given entity or context.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.