Triple
T9354956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lactuca |
E225113
|
entity |
| Predicate | agronomicRole |
P15634
|
FINISHED |
| Object | source of leafy salad crops |
—
|
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: source of leafy salad crops | Statement: [Lactuca, agronomicRole, source of leafy salad crops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agronomicRole Context triple: [Lactuca, agronomicRole, source of leafy salad crops]
-
A.
agriculturalRole
chosen
Indicates a role or function that an entity has within agricultural activities, production, or systems.
-
B.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
C.
farmSystemRole
Indicates the specific function, responsibility, or position an entity holds within an agricultural or farm management system.
-
D.
agriculturalEnvironment
Indicates that something exists in, is associated with, or is influenced by an agricultural or farming-related environment.
-
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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f99205c8190a5ad95926ef25497 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.