Triple
T25507724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redcrosse Knight |
E639289
|
entity |
| Predicate | slays |
P63277
|
FINISHED |
| Object | the dragon guarding Una’s parents |
—
|
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: the dragon guarding Una’s parents | Statement: [Redcrosse Knight, slays, the dragon guarding Una’s parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slays Context triple: [Redcrosse Knight, slays, the dragon guarding Una’s parents]
-
A.
slayedCreatureType
chosen
Indicates that an entity has killed or defeated a creature of a specified type.
-
B.
willKill
Indicates that one entity is destined or intends to cause the death of another entity in the future.
-
C.
blows
Indicates that one entity forcefully expels air or creates a current of air directed toward or acting upon another entity.
-
D.
diesInArmsOf
Indicates that one entity dies while being physically held or embraced by another entity.
-
E.
sharesSlainWith
Indicates that two or more entities have killed the same target or share responsibility for the same slaying event.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80749f88190a5c2a70e7370003b |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:47 p.m.