Triple
T27940185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgment of Paris 1976 wine tasting |
E700719
|
entity |
| Predicate | featuredRegion |
P151519
|
FINISHED |
| Object | California |
—
|
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: California | Statement: [Judgment of Paris 1976 wine tasting, featuredRegion, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredRegion Context triple: [Judgment of Paris 1976 wine tasting, featuredRegion, California]
-
A.
associatedRegionFeature
chosen
Indicates that something is linked or connected to a particular geographic or regional feature.
-
B.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
C.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
D.
primaryRegionDepicted
Indicates that a resource primarily depicts or visually represents a particular geographic or spatial region as its main subject.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
- 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_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 27, 2026, 7:17 p.m.