Triple
T36067235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vimoutiers |
E1043265
|
entity |
| Predicate | regionalProduct |
P108665
|
FINISHED |
| Object | Normandy cider |
—
|
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: Normandy cider | Statement: [Vimoutiers, regionalProduct, Normandy cider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalProduct Context triple: [Vimoutiers, regionalProduct, Normandy cider]
-
A.
regionalComponent
Indicates that one entity functions as a sub-region or constituent part within the larger geographic or administrative area represented by the other entity.
-
B.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
C.
suppliesRegion
Indicates that one entity provides goods, services, or resources to a specified geographic region.
-
D.
supplyRegion
Indicates that one entity serves as the source or provider of supplies, goods, or services to a specified geographic region.
-
E.
isRegional
chosen
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:08 p.m.