Triple
T25050463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AOC Bresse butter |
E627362
|
entity |
| Predicate | hasGeographicalLink |
P146651
|
FINISHED |
| Object | Bresse terroir |
—
|
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: Bresse terroir | Statement: [AOC Bresse butter, hasGeographicalLink, Bresse terroir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicalLink Context triple: [AOC Bresse butter, hasGeographicalLink, Bresse terroir]
-
A.
hasGeographicConnectionTo
chosen
Indicates a relationship where two entities are linked through a shared or relevant geographic feature, location, or spatial association.
-
B.
containsGeographicalReferences
Indicates that something includes mentions or information about specific geographical locations or features.
-
C.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
D.
typicalGeographicalAssociation
Indicates a usual or characteristic geographical connection between entities, such as a place commonly associated with a person, group, or phenomenon.
-
E.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:09 a.m.