Triple
T35482109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alayne Stone |
E1025495
|
entity |
| Predicate | trueHouseAllegiance |
P110386
|
FINISHED |
| Object | House Stark |
—
|
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 Stark | Statement: [Alayne Stone, trueHouseAllegiance, House Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trueHouseAllegiance Context triple: [Alayne Stone, trueHouseAllegiance, House Stark]
-
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.
hasCountryHouse
Indicates that one entity possesses or owns a house located in the countryside.
-
C.
hasAllyHouse
Indicates that one house maintains an alliance or supportive partnership with another house.
-
D.
stateAllegiance
chosen
Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
-
E.
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.
- 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.