Triple
T6440661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother (After the Fall) |
E138211
|
entity |
| Predicate | combatStyleAgainst |
P70645
|
FINISHED |
| Object | cooperative team-based combat |
—
|
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: cooperative team-based combat | Statement: [Mother (After the Fall), combatStyleAgainst, cooperative team-based combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatStyleAgainst Context triple: [Mother (After the Fall), combatStyleAgainst, cooperative team-based combat]
-
A.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
B.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
C.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
D.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
E.
opponentForceCharacteristic
Indicates a characteristic or attribute that describes the nature, capability, or condition of an opposing force.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06968c6a88190a623da9bd3152a66 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.