Triple
T4742093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Nassau-Siegen |
E105267
|
entity |
| Predicate | feudalTitleType |
P57399
|
FINISHED |
| Object | territorial title |
—
|
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: territorial title | Statement: [Count of Nassau-Siegen, feudalTitleType, territorial title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalTitleType Context triple: [Count of Nassau-Siegen, feudalTitleType, territorial title]
-
A.
typeOfFeudalGrant
Indicates the specific kind or category of feudal grant that characterizes the relationship between a grantor and a grantee within a feudal system.
-
B.
feudalType
chosen
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
C.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
D.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
E.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a7153881909eac451fc7566d25 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.