Triple
T17168767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akusha Dargwa |
E416672
|
entity |
| Predicate | neighboringVarieties |
P45557
|
FINISHED |
| Object | Akushin dialects of Dargwa |
—
|
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: Akushin dialects of Dargwa | Statement: [Akusha Dargwa, neighboringVarieties, Akushin dialects of Dargwa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringVarieties Context triple: [Akusha Dargwa, neighboringVarieties, Akushin dialects of Dargwa]
-
A.
hasNeighboringVariety
chosen
Indicates that one variety is geographically or spatially adjacent to another variety.
-
B.
closelyRelatedVariety
Indicates that one variety is very similar to another, differing only in minor or closely related characteristics.
-
C.
relatedCrop
Indicates that one crop has a meaningful association with another crop, such as complementary growth, rotation suitability, or shared characteristics.
-
D.
neighboringVineyard
Indicates that one vineyard is located adjacent to or very close to another vineyard.
-
E.
parentVariety
Indicates that one variety is the direct parent or source variety from which another variety is derived or developed.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f9173ee48190bc46622c78479603 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.