Triple
T29728493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folle Blanche |
E752252
|
entity |
| Predicate | historicallyPrizedIn |
P197659
|
FINISHED |
| Object | Armagnac |
—
|
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: Armagnac | Statement: [Folle Blanche, historicallyPrizedIn, Armagnac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPrizedIn Context triple: [Folle Blanche, historicallyPrizedIn, Armagnac]
-
A.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
-
B.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
-
C.
isHighlyPrized
Indicates that something is regarded with exceptional value, admiration, or importance, often being especially sought after or cherished.
-
D.
historicallySoughtBy
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
E.
isHistoricAward
Indicates that an award is recognized as historically significant, typically due to its age, legacy, or long-standing impact.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: April 28, 2026, 7:40 p.m.