Triple
T19017936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elabered |
E465403
|
entity |
| Predicate | hasAgriculturalPotential |
P121969
|
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: [Elabered, hasAgriculturalPotential, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgriculturalPotential Context triple: [Elabered, hasAgriculturalPotential, high]
-
A.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
B.
hasFertileLand
chosen
Indicates that one entity possesses or contains land that is capable of supporting abundant plant growth or agricultural production.
-
C.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
-
D.
yieldPotential
Indicates the expected amount or capacity of output, production, or benefit that something can generate under given conditions.
-
E.
locatedInAgriculturalRegion
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dd0e6c8190a6dc6af1f7901299 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.