Triple
T4953773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nodaway Valley |
E111230
|
entity |
| Predicate | hasDominantCommunityType |
P3292
|
FINISHED |
| Object | farming communities |
—
|
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: farming communities | Statement: [Nodaway Valley, hasDominantCommunityType, farming communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantCommunityType Context triple: [Nodaway Valley, hasDominantCommunityType, farming communities]
-
A.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
-
B.
hasDominantSpecies
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
C.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
D.
hasMajorCommunity
Indicates that an entity possesses a primary or significantly large community associated with it.
-
E.
dominantComposition
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b82dd88190adfb08c3b3191fe0 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.