Triple
T16633795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connor MacLeod |
E404145
|
entity |
| Predicate | ruleOfImmortals |
P123664
|
FINISHED |
| Object | can only be killed by beheading |
—
|
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: can only be killed by beheading | Statement: [Connor MacLeod, ruleOfImmortals, can only be killed by beheading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleOfImmortals Context triple: [Connor MacLeod, ruleOfImmortals, can only be killed by beheading]
-
A.
notImmortal
Indicates that the entity does not possess immortality and is subject to death or an end to its existence.
-
B.
sharesImmortalityWith
Indicates that one entity grants or mutually possesses an immortal or deathless state together with another entity.
-
C.
immortality
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
D.
ruleOfLife
Indicates a guiding principle, norm, or code that governs how an entity should live or behave.
-
E.
becomesImmortalIn
Indicates that an entity transitions into a state of immortality within a specified context, time, or medium.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e7d4a48190a9b4a14ecbb2a14b |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.