Triple
T28950405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nisa PDO |
E730995
|
entity |
| Predicate | hasLegalProtectionIn |
P38312
|
FINISHED |
| Object | European Union |
—
|
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: European Union | Statement: [Nisa PDO, hasLegalProtectionIn, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalProtectionIn Context triple: [Nisa PDO, hasLegalProtectionIn, European Union]
-
A.
isLegallyProtected
Indicates that an entity is safeguarded by law, granting it specific rights or restrictions against harm, use, or alteration.
-
B.
isProtectedByLawIn
chosen
Indicates that an entity is safeguarded or granted legal protection within a specified jurisdiction or legal framework.
-
C.
legalProtectionFor
Indicates that one entity provides or is subject to legal safeguards, rights, or defenses in favor of another entity or interest.
-
D.
hasLegalProtectionSince
Indicates that an entity has been under formal legal protection starting from a specified date or point in time.
-
E.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 8:43 a.m.