Triple
T38240376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Umber |
E1013744
|
entity |
| Predicate | loyaltyPattern |
P76252
|
FINISHED |
| Object | Historically loyal to House Stark |
—
|
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: Historically loyal to House Stark | Statement: [House Umber, loyaltyPattern, Historically loyal to House Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyPattern Context triple: [House Umber, loyaltyPattern, Historically loyal to House Stark]
-
A.
loyaltyMechanism
Indicates a mechanism or process through which loyalty is established, maintained, or reinforced between entities.
-
B.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyDimension
chosen
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
-
E.
loyaltyArc
Indicates a character’s progression in loyalty toward another entity, typically showing how trust, allegiance, or faithfulness strengthens, weakens, or transforms over time.
- 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.