Triple
T27761650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bocksbeutel |
E701484
|
entity |
| Predicate | allowedFor |
P273
|
FINISHED |
| Object | certain quality wines from specified regions |
—
|
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: certain quality wines from specified regions | Statement: [Bocksbeutel, allowedFor, certain quality wines from specified regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedFor Context triple: [Bocksbeutel, allowedFor, certain quality wines from specified regions]
-
A.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
C.
isStillAllowedFor
Indicates that one entity continues to have permission or authorization to access, use, or perform something in relation to another entity.
-
D.
admitsFrom
Indicates that one entity accepts or enrolls individuals coming from another specified source or institution.
-
E.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 4:27 p.m.