Triple
T14778798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbie Mills |
E347334
|
entity |
| Predicate | combatAgainst |
P98579
|
FINISHED |
| Object | supernatural threats |
—
|
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: supernatural threats | Statement: [Abbie Mills, combatAgainst, supernatural threats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatAgainst Context triple: [Abbie Mills, combatAgainst, supernatural threats]
-
A.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
B.
combat
chosen
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
C.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
-
D.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
E.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9c7cac8190ba900df95e42e318 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.