Triple
T27970962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Procanico |
E706352
|
entity |
| Predicate | rarelyUsedFor |
P7974
|
FINISHED |
| Object | varietal bottlings |
—
|
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: varietal bottlings | Statement: [Procanico, rarelyUsedFor, varietal bottlings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rarelyUsedFor Context triple: [Procanico, rarelyUsedFor, varietal bottlings]
-
A.
notTypicallyUsedFor
chosen
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
B.
usedLessIn
Indicates that one entity is used with a lower frequency or intensity compared to another entity.
-
C.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
notAutomaticallyUsedBy
Indicates that something is not used by another entity in an automatic or default manner and instead requires explicit action or configuration to be used.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b35079c819084779003fe29410d |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:38 p.m.