Triple
T8271640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medronho brandy |
E193441
|
entity |
| Predicate | legalStatusInPortugal |
P82432
|
FINISHED |
| Object | regulated spirit |
—
|
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: regulated spirit | Statement: [medronho brandy, legalStatusInPortugal, regulated spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInPortugal Context triple: [medronho brandy, legalStatusInPortugal, regulated spirit]
-
A.
roleInPortugal
Indicates that an entity holds or has held a specific role, position, or function within the context of Portugal.
-
B.
limitedPortugalTo
Indicates that something is restricted in scope, effect, or applicability specifically to Portugal.
-
C.
legalStatusInEsperantoCommunity
Indicates the legal recognition or standing an entity holds within the Esperanto-speaking community or its institutions.
-
D.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
E.
legalStatusInEuropeanUnion
Indicates the legal status or standing that an entity holds within the jurisdictional framework of the European Union.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7986f8cc8190a529dda980dd6e98 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:50 p.m.