Triple
T35200018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Independence From Technology |
E1016371
|
entity |
| Predicate | notableAttackOn |
P206872
|
FINISHED |
| Object | Will Caster |
E1016372
|
NE 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: Will Caster | Statement: [Revolutionary Independence From Technology, notableAttackOn, Will Caster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAttackOn Context triple: [Revolutionary Independence From Technology, notableAttackOn, Will Caster]
-
A.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
B.
notableAttackLocation
Indicates the specific place where a significant or notable attack occurred in relation to the subject.
-
C.
knownAttacks
Indicates that one entity is aware of, or has information about, specific attacks associated with another entity.
-
D.
notableAdversary
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
-
E.
notableActionAt
Indicates that an entity performed or was involved in a significant action or event at a specific location or point in time.
- F. None of above. chosen
Provenance (5 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb29f3b48190a480821ffc076d98 |
completed | June 21, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.