Triple
T38240433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Glover |
E1013745
|
entity |
| Predicate | fealtyTradition |
P1201
|
FINISHED |
| Object | Ancient loyalty to the Kings in the North |
—
|
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: Ancient loyalty to the Kings in the North | Statement: [House Glover, fealtyTradition, Ancient loyalty to the Kings in the North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fealtyTradition Context triple: [House Glover, fealtyTradition, Ancient loyalty to the Kings in the North]
-
A.
allegiance
chosen
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
B.
hasFaithfulOfTradition
Indicates that an entity has followers or adherents who remain loyal to and practice a particular tradition.
-
C.
chivalricTradition
Indicates a relationship where behaviors, values, or actions conform to or are guided by the codes and ideals of chivalry.
-
D.
feud
Indicates a prolonged, mutual state of hostility or conflict between two or more parties.
-
E.
nobleTradition
Indicates a relationship where an entity upholds, follows, or is associated with a long-established and esteemed custom or practice.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.