Triple
T18283141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashildr |
E437912
|
entity |
| Predicate | madeImmortalUsing |
P131171
|
FINISHED |
| Object | Mire repair kit |
—
|
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: Mire repair kit | Statement: [Ashildr, madeImmortalUsing, Mire repair kit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeImmortalUsing Context triple: [Ashildr, madeImmortalUsing, Mire repair kit]
-
A.
becomesImmortalIn
Indicates that an entity transitions into a state of immortality within a specified context, time, or medium.
-
B.
immortality
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
C.
notImmortal
Indicates that the entity does not possess immortality and is subject to death or an end to its existence.
-
D.
sharesImmortalityWith
Indicates that one entity grants or mutually possesses an immortal or deathless state together with another entity.
-
E.
ruleOfImmortals
Indicates a governing or authoritative relationship exercised by immortal beings over others.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50057c5c881909fcda72f4a98c8c3 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.