Triple
T18948216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahr wine region |
E463570
|
entity |
| Predicate | hasPDOStatus |
P46212
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ahr wine region, hasPDOStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPDOStatus Context triple: [Ahr wine region, hasPDOStatus, yes]
-
A.
PDOStatus
Indicates that an entity’s status or condition is defined or tracked according to the PDO (Process Data Object) state within a communication or control system.
-
B.
cheeseHasPDOStatus
chosen
Indicates that a cheese possesses Protected Designation of Origin (PDO) status under relevant geographical indication regulations.
-
C.
hasDialectStatus
Indicates that one language variety holds a particular dialect-related status or classification in relation to another language or linguistic standard.
-
D.
hasExistenceStatus
Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
-
E.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.