Triple
T34569912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuburger |
E887596
|
entity |
| Predicate | traditionallyGrownAlong |
P61339
|
FINISHED |
| Object | Danube River |
—
|
NE NERFINISHED |
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: Danube River | Statement: [Neuburger, traditionallyGrownAlong, Danube River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyGrownAlong Context triple: [Neuburger, traditionallyGrownAlong, Danube River]
-
A.
cultivatedBy
Indicates that something (such as land, crops, or plants) is grown, tended, or developed through the efforts or care of a particular agent.
-
B.
cultivatedAlong
Indicates that one entity is grown or farmed in proximity to or in parallel with another entity, typically within the same area or setting.
-
C.
exclusivelyGrownIn
Indicates that something is cultivated or produced only within a specific geographic area or location and nowhere else.
-
D.
cultivatedPrimarilyIn
chosen
Indicates that something is mainly grown, produced, or farmed in a particular place or environment.
-
E.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 1, 2026, 2:02 a.m.