Triple
T13189732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaime Lannister |
E313950
|
entity |
| Predicate | oathInvolves |
P16811
|
FINISHED |
| Object | returning Arya Stark and Sansa 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: returning Arya Stark and Sansa Stark | Statement: [Jaime Lannister, oathInvolves, returning Arya Stark and Sansa Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathInvolves Context triple: [Jaime Lannister, oathInvolves, returning Arya Stark and Sansa Stark]
-
A.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
B.
hasOathTo
chosen
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
containsOathBy
Indicates that one entity (such as a text, document, or statement) includes or features an oath made by another entity.
-
D.
oathsAbout
Indicates that one entity makes or concerns a formal oath regarding another entity or subject.
-
E.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.