Triple
T23166597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Blossom Festival |
E578725
|
entity |
| Predicate | focusesOnAgriculture |
P93731
|
FINISHED |
| Object | apple orchards |
—
|
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: apple orchards | Statement: [Apple Blossom Festival, focusesOnAgriculture, apple orchards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnAgriculture Context triple: [Apple Blossom Festival, focusesOnAgriculture, apple orchards]
-
A.
agriculturalFocus
chosen
Indicates that an entity is primarily concerned with, oriented toward, or specializing in agriculture or farming-related activities.
-
B.
viewOnAgriculture
Indicates a stance, opinion, or perspective that an entity holds regarding agriculture or agricultural practices.
-
C.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
D.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
E.
representsAgriculture
Indicates that one entity serves as an example, instance, or embodiment of agriculture in relation to another entity.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2c923c81908b58811fffdcf932 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.