Triple
T25953544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebreton |
E654030
|
entity |
| Predicate | hasRegionOfCulturalOrigin |
P159764
|
FINISHED |
| Object | Brittany |
—
|
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: Brittany | Statement: [Lebreton, hasRegionOfCulturalOrigin, Brittany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionOfCulturalOrigin Context triple: [Lebreton, hasRegionOfCulturalOrigin, Brittany]
-
A.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
B.
hasEthnicOrRegionalOrigin
chosen
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
C.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
-
D.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
E.
hasFamilyCulturalSphere
Indicates that one entity belongs to, or is associated with, the family-related cultural sphere or tradition of 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 22, 2026, 8:44 a.m.