Triple
T35482077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen in the North |
E1025494
|
entity |
| Predicate | swornVassals |
P7255
|
FINISHED |
| Object | Houses of the North |
—
|
NE NERFINISHED |
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: Houses of the North | Statement: [Queen in the North, swornVassals, Houses of the North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swornVassals Context triple: [Queen in the North, swornVassals, Houses of the North]
-
A.
vassalsOf
chosen
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.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
D.
vassalOrAllyOf
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
-
E.
heldFief
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.