Triple
T11844435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Alcaraz |
E281735
|
entity |
| Predicate | typeOfVassalage |
P57399
|
FINISHED |
| Object | tributary vassalage |
—
|
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: tributary vassalage | Statement: [Treaty of Alcaraz, typeOfVassalage, tributary vassalage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVassalage Context triple: [Treaty of Alcaraz, typeOfVassalage, tributary vassalage]
-
A.
vassalsOf
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
B.
vassalageOver
Indicates a hierarchical feudal relationship in which one party is a vassal subordinate to and owing allegiance or obligations to another.
-
C.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
D.
feudalType
chosen
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
E.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65a597c8190b09f57463b279afc |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.