Triple
T24729335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breton people |
E618240
|
entity |
| Predicate | historicalDuchy |
P156004
|
FINISHED |
| Object | Duchy of 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: Duchy of Brittany | Statement: [Breton people, historicalDuchy, Duchy of Brittany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDuchy Context triple: [Breton people, historicalDuchy, Duchy of Brittany]
-
A.
wasDuchyWithin
Indicates that a political entity held the status of a duchy within the territorial or administrative boundaries of another entity.
-
B.
countryDuringHabsburgPeriod
Indicates that a country existed under, was ruled by, or was part of the Habsburg realms during the historical Habsburg period.
-
C.
existedAsSeparateDuchyUntil
chosen
Indicates that an entity functioned as an independent duchy in its own right up to a specified end date.
-
D.
partOfHistoricalMonarchy
Indicates that an entity belonged to, was included within, or was under the authority of a specific historical monarchy.
-
E.
countryDuringAustrianEmpirePeriod
Indicates that a given country existed or was recognized as such during the historical period of the Austrian Empire.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 4:01 a.m.