Triple
T31347339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volturnus River region |
E799483
|
entity |
| Predicate | hasAgriculturalImportanceFor |
P14281
|
FINISHED |
| Object | nearby settlements |
—
|
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: nearby settlements | Statement: [Volturnus River region, hasAgriculturalImportanceFor, nearby settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgriculturalImportanceFor Context triple: [Volturnus River region, hasAgriculturalImportanceFor, nearby settlements]
-
A.
hasEconomicImportanceFor
chosen
Indicates that one entity holds economic value, benefit, or significance for another entity.
-
B.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
C.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
D.
widelyCultivatedIn
Indicates that something is grown extensively or on a large scale within a particular place or region.
-
E.
cultivatedPrimarilyIn
Indicates that something is mainly grown, produced, or farmed in a particular place or environment.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f19a79c81909647d8eef6706e44 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.