Triple
T6523323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barolo |
E151240
|
entity |
| Predicate | styleReputation |
P29718
|
FINISHED |
| Object | powerful |
—
|
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: powerful | Statement: [Barolo, styleReputation, powerful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleReputation Context triple: [Barolo, styleReputation, powerful]
-
A.
fashionReputation
chosen
Indicates the perceived status or esteem an entity holds within the context of fashion, based on how its style, taste, or influence is judged by others.
-
B.
designReputation
Indicates the perceived quality or standing of an entity based on others’ judgments of its design.
-
C.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
D.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
E.
performanceReputation
Indicates the perceived quality or reliability of an entity’s past or expected performance as judged by others.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad970afc81909d3231203eacf413 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.