Triple
T21709450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maius |
E535860
|
entity |
| Predicate | associatedWithAgriculturalActivities |
P15634
|
FINISHED |
| Object | planting |
—
|
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: planting | Statement: [Maius, associatedWithAgriculturalActivities, planting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAgriculturalActivities Context triple: [Maius, associatedWithAgriculturalActivities, planting]
-
A.
hasAgriculturalAssociation
Indicates that there exists a formal or recognized connection between an entity and an agricultural organization, group, or activity.
-
B.
agriculturalRole
chosen
Indicates a role or function that an entity has within agricultural activities, production, or systems.
-
C.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
D.
representsAgriculture
Indicates that one entity serves as an example, instance, or embodiment of agriculture in relation to another entity.
-
E.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5321d34819091f3cd03f7b407c0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.