Triple
T7944759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFA Cup |
E184471
|
entity |
| Predicate | allowsGiantKillings |
P79959
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FFA Cup, allowsGiantKillings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsGiantKillings Context triple: [FFA Cup, allowsGiantKillings, true]
-
A.
considersKilling
Indicates that one entity is contemplating or evaluating the possibility of killing another entity.
-
B.
willKill
Indicates that one entity is destined or intends to cause the death of another entity in the future.
-
C.
ultimatelyRefusesToKill
Indicates that an entity, despite prior opportunity or intent, finally decides not to kill another entity.
-
D.
numberOfPerpetratorsKilled
Indicates the count of perpetrators who were killed in the context of the described event or incident.
-
E.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b285d3881909b2ac0b395538a8a |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf788db1c8190839523e7777961d6 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:09 p.m.