Triple
T19467975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equatoria region |
E487047
|
entity |
| Predicate | agriculturalPotential |
P32569
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Equatoria region, agriculturalPotential, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agriculturalPotential Context triple: [Equatoria region, agriculturalPotential, high]
-
A.
yieldPotential
chosen
Indicates the expected amount or capacity of output, production, or benefit that something can generate under given conditions.
-
B.
agriculturalEnvironment
Indicates that something exists in, is associated with, or is influenced by an agricultural or farming-related environment.
-
C.
shareAgriculturalFeature
Indicates that two or more entities possess the same agricultural characteristic, condition, or resource.
-
D.
agriculturalImpact
Indicates the effect that an action, condition, or entity has on agricultural systems, productivity, or practices.
-
E.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e4b230819097c8804ee91988ea |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.