Triple
T2957939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sancerre |
E79976
|
entity |
| Predicate | recognizedAsAOC |
P16569
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [Sancerre, recognizedAsAOC, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsAOC Context triple: [Sancerre, recognizedAsAOC, 1936]
-
A.
hasAOC
Indicates that one entity possesses, is associated with, or is characterized by a specific Area of Concern (AOC).
-
B.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
C.
denominationOfOrigin
chosen
Indicates a legally recognized origin relationship where a product’s quality or characteristics are specifically attributable to being produced in a particular geographic region.
-
D.
recognizedByCouncil
Indicates that an entity has been formally acknowledged or approved by a council as meeting its criteria or standards.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992b33e081909d22a19d5064c47d |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.