Triple
T7225439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chianti |
E150366
|
entity |
| Predicate | traditionalContainer |
P22942
|
FINISHED |
| Object | fiasco |
—
|
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: fiasco | Statement: [Chianti, traditionalContainer, fiasco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalContainer Context triple: [Chianti, traditionalContainer, fiasco]
-
A.
traditionalStructure
Indicates that something follows or embodies a customary, historically established form, pattern, or organizational framework.
-
B.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
C.
traditionalVessel
chosen
Indicates that one entity is a vessel or container that follows traditional, customary, or historically established forms, designs, or uses in relation to another entity.
-
D.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
E.
traditionalView
Indicates that one entity holds or represents a conventional, long-established perspective or interpretation about another entity or topic.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.