Triple
T2441303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doux |
E53280
|
entity |
| Predicate | hasLegalDefinitionScope |
P25835
|
FINISHED |
| Object | European Union wine regulations |
—
|
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: European Union wine regulations | Statement: [Doux, hasLegalDefinitionScope, European Union wine regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalDefinitionScope Context triple: [Doux, hasLegalDefinitionScope, European Union wine regulations]
-
A.
legalScope
chosen
Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
-
B.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
-
D.
hasLegalFunction
Indicates that an entity performs, fulfills, or is assigned a specific legal role, duty, or function within a legal or regulatory context.
-
E.
hasScopeRule
Indicates that a given entity is governed, constrained, or interpreted according to a particular scope-defining rule.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.