Triple
T3755670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wine Bar George |
E82040
|
entity |
| Predicate | hasTitleOfCurator |
P41897
|
FINISHED |
| Object | Master Sommelier |
—
|
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: Master Sommelier | Statement: [Wine Bar George, hasTitleOfCurator, Master Sommelier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleOfCurator Context triple: [Wine Bar George, hasTitleOfCurator, Master Sommelier]
-
A.
hasCuratorialRole
Indicates that an entity holds a curatorial position or responsibility in relation to another entity, such as overseeing its selection, organization, or presentation.
-
B.
titleHolderIs
chosen
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
titleBeforeAccession
Indicates that the specified title was held by an entity prior to its accession to a higher rank, office, or status.
-
D.
originalHolderTitle
Indicates the formal title or designation held by the entity that originally possessed or held another entity.
-
E.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb96dd908190b787b112ecd519df |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.