Triple
T27294118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Brionne |
E688711
|
entity |
| Predicate | feudalDomainType |
P57399
|
FINISHED |
| Object | seigneury |
—
|
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: seigneury | Statement: [Lord of Brionne, feudalDomainType, seigneury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalDomainType Context triple: [Lord of Brionne, feudalDomainType, seigneury]
-
A.
feudalType
chosen
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
B.
feudType
Indicates the specific kind or category of ongoing conflict or long-standing hostility that exists between entities.
-
C.
isFeudal
Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
-
D.
feudalBasis
Indicates that one entity is related to another through a feudal relationship, such as obligations, rights, or structures characteristic of a feudal system.
-
E.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6277e806c819085dbcbddb9d86af1 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:17 a.m.