Triple
T24670644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limagne plain vicinity |
E610819
|
entity |
| Predicate | typicalAgriculturalUse |
P49740
|
FINISHED |
| Object | arable farming |
—
|
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: arable farming | Statement: [Limagne plain vicinity, typicalAgriculturalUse, arable farming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgriculturalUse Context triple: [Limagne plain vicinity, typicalAgriculturalUse, arable farming]
-
A.
agricultureUse
chosen
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
B.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
C.
livestockUse
Indicates how an entity is used or managed in relation to livestock, such as for raising, feeding, housing, or supporting livestock activities.
-
D.
plantUse
Indicates that a plant is used for a particular purpose, function, or application.
-
E.
hasAgriculturalType
Indicates that an entity is associated with or classified by a specific type or category of agriculture.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 2:42 a.m.