Triple
T35482108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alayne Stone |
E1025495
|
entity |
| Predicate | claimedHouseAllegiance |
P190709
|
FINISHED |
| Object | House Baelish |
—
|
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: House Baelish | Statement: [Alayne Stone, claimedHouseAllegiance, House Baelish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedHouseAllegiance Context triple: [Alayne Stone, claimedHouseAllegiance, House Baelish]
-
A.
houseSeatAllegiance
Indicates that a noble house holds loyalty or sworn allegiance to a particular higher authority, such as a liege, faction, or realm.
-
B.
hadAllegiance
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
C.
stateAllegiance
Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
-
D.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
E.
hasAllyHouse
Indicates that one house maintains an alliance or supportive partnership with another house.
- F. None of above. chosen
Provenance (4 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_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:04 p.m.