Triple
T37353050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvetia, Oregon |
E927375
|
entity |
| Predicate | featuredFarm |
P72098
|
FINISHED |
| Object | Roloff Farms |
E927373
|
NE 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: Roloff Farms | Statement: [Helvetia, Oregon, featuredFarm, Roloff Farms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredFarm Context triple: [Helvetia, Oregon, featuredFarm, Roloff Farms]
-
A.
shareAgriculturalFeature
Indicates that two or more entities possess the same agricultural characteristic, condition, or resource.
-
B.
farmSystemOf
Indicates that one entity is the agricultural or farming system to which another entity belongs or with which it is associated.
-
C.
farmingStructure
chosen
Indicates that one entity is a structure or facility used for farming-related activities in relation to another entity.
-
D.
farmingCharacteristics
Indicates the specific methods, practices, or attributes that characterize how farming is conducted in relation to an entity.
-
E.
servesAsFarmSystemFor
Indicates that one entity functions as a developmental or feeder system that supplies trained or prepared resources (such as players, talent, or products) to another entity.
- F. None of above.
Provenance (4 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a7df6a648190b125d691ad09adff |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.