Triple
T35482347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer |
E1025500
|
entity |
| Predicate | wargBondWith |
P108873
|
FINISHED |
| Object | Bran 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: Bran Stark | Statement: [Summer, wargBondWith, Bran Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wargBondWith Context triple: [Summer, wargBondWith, Bran Stark]
-
A.
wargBond
chosen
Indicates a special bond or partnership between a warg and another entity, typically involving loyalty, cooperation, or shared purpose.
-
B.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
C.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
-
D.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
E.
canBondWith
Indicates that one entity has the capability or compatibility to form a bond or connection with 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_69f76dfbcdd881908c7b0b6bc502252b |
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.