Triple
T24431180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashley Williams |
E616004
|
entity |
| Predicate | combatClass |
P155027
|
FINISHED |
| Object | Soldier |
—
|
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: Soldier | Statement: [Ashley Williams, combatClass, Soldier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatClass Context triple: [Ashley Williams, combatClass, Soldier]
-
A.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
B.
combatView
Indicates a perspective or representation of entities engaged in combat or battle-related interaction.
-
C.
primaryCombatType
chosen
Indicates the main form or style of combat that an entity primarily uses or is associated with.
-
D.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
E.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.