Triple
T30726186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiritsugu Emiya |
E782284
|
entity |
| Predicate | commandSealsOn |
P181674
|
FINISHED |
| Object | Saber (Artoria Pendragon) |
—
|
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: Saber (Artoria Pendragon) | Statement: [Kiritsugu Emiya, commandSealsOn, Saber (Artoria Pendragon)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandSealsOn Context triple: [Kiritsugu Emiya, commandSealsOn, Saber (Artoria Pendragon)]
-
A.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
B.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
C.
sealingMechanism
Indicates a relationship where one entity functions as or provides the means by which another entity is sealed or made airtight/watertight.
-
D.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
E.
requiresSeal
Indicates that one entity must be sealed or have a seal applied as a necessary condition for another entity’s use, validity, or completion.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 29, 2026, 8:36 p.m.