Triple
T26867187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banaganapalle |
E676504
|
entity |
| Predicate | mangoVarietyOrigin |
P71873
|
FINISHED |
| Object | Banaganapalle mango |
—
|
NE NERFINISHED |
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: Banaganapalle mango | Statement: [Banaganapalle, mangoVarietyOrigin, Banaganapalle mango]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mangoVarietyOrigin Context triple: [Banaganapalle, mangoVarietyOrigin, Banaganapalle mango]
-
A.
cultivarOrigin
chosen
Indicates that a particular plant cultivar was originally developed, bred, or derived from a specified source location, population, or lineage.
-
B.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
C.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
-
D.
cultivatedInCountry
Indicates that something (such as a crop, plant, or organism) is grown or produced through cultivation within the specified country.
-
E.
notableVarieties
Indicates that there are specific, distinguished types or versions associated with an entity that are recognized as notable.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e98eb7881909d8b323c85ec787f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:29 a.m.