Triple
T27940217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgment of Paris 1976 wine tasting |
E700719
|
entity |
| Predicate | organizerProfession |
P113517
|
FINISHED |
| Object | wine merchant |
—
|
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: wine merchant | Statement: [Judgment of Paris 1976 wine tasting, organizerProfession, wine merchant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizerProfession Context triple: [Judgment of Paris 1976 wine tasting, organizerProfession, wine merchant]
-
A.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
B.
organizers
Indicates that one or more entities are responsible for planning, coordinating, or managing an event, activity, or group.
-
C.
organizerIndustry
chosen
Indicates the industry or business sector in which the organizer operates or is classified.
-
D.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
E.
co-organizerOf
Indicates that an entity shares responsibility with others in planning, coordinating, or managing an event, project, or activity.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 7:17 p.m.