Triple
T4151413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Forest ham |
E89913
|
entity |
| Predicate | hasProtectedStatusAbbreviation |
P54637
|
FINISHED |
| Object | PGI |
—
|
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: PGI | Statement: [Black Forest ham, hasProtectedStatusAbbreviation, PGI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedStatusAbbreviation Context triple: [Black Forest ham, hasProtectedStatusAbbreviation, PGI]
-
A.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
B.
isProtectedAreaStatus
Indicates that an entity has a designated protection status, typically signifying legal or formal recognition as a protected area.
-
C.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
D.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- F. None of above. chosen
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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af033d94888190b34349e355b874ef |
completed | March 9, 2026, 5:28 p.m. |
Created at: March 9, 2026, 3:44 p.m.