Triple
T9598575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judean Hills wine region |
E231792
|
entity |
| Predicate | hasViticulturalHistory |
P12089
|
FINISHED |
| Object | ancient |
—
|
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: ancient | Statement: [Judean Hills wine region, hasViticulturalHistory, ancient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViticulturalHistory Context triple: [Judean Hills wine region, hasViticulturalHistory, ancient]
-
A.
viticultureHistory
chosen
Indicates the historical development, practices, and events related to grape cultivation and winemaking over time.
-
B.
hasWineMakingTradition
Indicates that a place or group has an established, culturally recognized history and practice of producing wine.
-
C.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
-
D.
foundedAsVineyard
Indicates that an organization, estate, or property was originally established as a vineyard.
-
E.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a366d3481908db62e476958eafe |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.