Triple
T30041130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fosca |
E763304
|
entity |
| Predicate | agriculturalProductType |
P137337
|
FINISHED |
| Object | Andean crops |
—
|
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: Andean crops | Statement: [Fosca, agriculturalProductType, Andean crops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agriculturalProductType Context triple: [Fosca, agriculturalProductType, Andean crops]
-
A.
agriculturalProduce
Indicates that one entity is an agricultural product (such as crops or livestock-derived goods) produced by or associated with another entity.
-
B.
hasAgriculturalType
chosen
Indicates that an entity is associated with or classified by a specific type or category of agriculture.
-
C.
typeOfFarmProductInDispute
Indicates that a specific kind of farm product is the subject of a disagreement, conflict, or legal dispute between parties.
-
D.
traditionalAgriculturalProduct
Indicates that something is recognized as an agricultural product produced using long-established, customary methods and practices.
-
E.
agriculturalOutputDestination
Indicates the destination or recipient to which agricultural output is directed or delivered.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d8525881909915ac704ab1ac30 |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:53 p.m.