Triple
T25336440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catawba |
E635290
|
entity |
| Predicate | regionCultivated |
P95212
|
FINISHED |
| Object | Ohio River Valley |
—
|
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: Ohio River Valley | Statement: [Catawba, regionCultivated, Ohio River Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCultivated Context triple: [Catawba, regionCultivated, Ohio River Valley]
-
A.
cultivatedInRegion
chosen
Indicates that something (such as a crop or plant) is grown or produced through cultivation within a specified geographic region.
-
B.
cultivatedAlong
Indicates that one entity is grown or farmed in proximity to or in parallel with another entity, typically within the same area or setting.
-
C.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
-
D.
isCultivated
Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
-
E.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 1:32 p.m.