Triple
T37190235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goëlo |
E921431
|
entity |
| Predicate | wasFeudalTerritoryOf |
P87619
|
FINISHED |
| Object | Breton nobility |
—
|
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: Breton nobility | Statement: [Goëlo, wasFeudalTerritoryOf, Breton nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFeudalTerritoryOf Context triple: [Goëlo, wasFeudalTerritoryOf, Breton nobility]
-
A.
formerFiefOf
chosen
Indicates that a territory or domain was previously under the control or jurisdiction of a specified lord, ruler, or political entity as a fief.
-
B.
wasCoreTerritoryOf
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
C.
wasDuchyWithin
Indicates that a political entity held the status of a duchy within the territorial or administrative boundaries of another entity.
-
D.
kingdomAnnexedBy
Indicates that a kingdom has been taken over and incorporated into another political entity through annexation.
-
E.
territoryLaterControlledBy
Indicates that a territory was subsequently governed, ruled, or administered by a specified controlling entity after an earlier period.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.