Triple
T35481939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Celtigar |
E1025491
|
entity |
| Predicate | typeOfVassal |
P203612
|
FINISHED |
| Object | Crownlands vassal |
—
|
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: Crownlands vassal | Statement: [House Celtigar, typeOfVassal, Crownlands vassal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVassal Context triple: [House Celtigar, typeOfVassal, Crownlands vassal]
-
A.
servantType
Indicates the specific role or category of service that one entity performs in relation to another.
-
B.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
C.
vassalsOf
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
D.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
E.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
- F. None of above. chosen
Provenance (4 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_6a01b31a5b408190abde68df45a82c81 |
completed | May 11, 2026, 10:44 a.m. |
Created at: May 3, 2026, 4:04 p.m.