Triple
T31947202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Miller |
E815683
|
entity |
| Predicate | hasCombatExperience |
P73817
|
FINISHED |
| Object | post-outbreak survival |
—
|
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: post-outbreak survival | Statement: [Tommy Miller, hasCombatExperience, post-outbreak survival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombatExperience Context triple: [Tommy Miller, hasCombatExperience, post-outbreak survival]
-
A.
hasCombat
chosen
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
B.
sawCombatAgainst
Indicates that one entity directly engaged in combat or battle against another entity.
-
C.
hasPerspectiveOnCombat
Indicates a relationship where an entity holds a particular viewpoint, attitude, or stance regarding combat or warfare.
-
D.
sawCombat
Indicates that an entity directly participated in active military or armed conflict.
-
E.
hasCombatEnvironment
Indicates that an entity is associated with, occurs within, or is characterized by a particular combat or battlefield environment.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a03433dd64c8190ab620709153b6278 |
completed | May 12, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_6a034107e53881909127bac98cac3429 |
completed | May 12, 2026, 3:02 p.m. |
Created at: May 1, 2026, 12:07 a.m.