Triple
T24319708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comtesse de Boulogne |
E612924
|
entity |
| Predicate | titleInFeudalSystem |
P106301
|
FINISHED |
| Object | countship of Boulogne |
—
|
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: countship of Boulogne | Statement: [Comtesse de Boulogne, titleInFeudalSystem, countship of Boulogne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInFeudalSystem Context triple: [Comtesse de Boulogne, titleInFeudalSystem, countship of Boulogne]
-
A.
feudalTitleOver
Indicates a hierarchical feudal relationship in which one party holds formal title-based authority or overlordship over another.
-
B.
isFeudalTitle
chosen
Indicates that the subject is a title associated with a feudal hierarchy, such as those held within a system of lords, vassals, and land-based obligations.
-
C.
feudalRights
Indicates that one party holds traditional feudal privileges, claims, or entitlements over another party or resource within a hierarchical lord–vassal structure.
-
D.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
E.
feudName
Indicates a named rivalry or ongoing conflict that exists between entities.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292aa63fc8190a874367c9010f283 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:48 a.m.