Triple
T33954532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Flip of a Coin |
E870529
|
entity |
| Predicate | featuresCombat |
P47597
|
FINISHED |
| Object | third-person melee 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: third-person melee combat | Statement: [A Flip of a Coin, featuresCombat, third-person melee combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCombat Context triple: [A Flip of a Coin, featuresCombat, third-person melee combat]
-
A.
featuresBattle
chosen
Indicates that one entity includes, presents, or involves a battle as a significant element or event.
-
B.
combatApplication
Indicates the application or use of something (such as skills, tactics, or equipment) within a combat or fighting context.
-
C.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
D.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
E.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:49 a.m.