Triple
T4994226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giants (Greek mythology) |
E112204
|
entity |
| Predicate | canBeKilledOnlyBy |
P44055
|
FINISHED |
| Object | a god aided by a mortal |
—
|
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: a god aided by a mortal | Statement: [Giants (Greek mythology), canBeKilledOnlyBy, a god aided by a mortal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeKilledOnlyBy Context triple: [Giants (Greek mythology), canBeKilledOnlyBy, a god aided by a mortal]
-
A.
killedBy
Indicates that one entity caused the death of another entity.
-
B.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
C.
methodOfDefeat
chosen
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
D.
ultimatelyRefusesToKill
Indicates that an entity, despite prior opportunity or intent, finally decides not to kill another entity.
-
E.
killedAlongWith
Indicates that one entity was killed at the same time and in the same event or circumstance as another entity.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.