Triple
T16011105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bouncer |
E388337
|
entity |
| Predicate | hasAttackType |
P4333
|
FINISHED |
| Object | ranged attacks |
—
|
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: ranged attacks | Statement: [Bouncer, hasAttackType, ranged attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttackType Context triple: [Bouncer, hasAttackType, ranged attacks]
-
A.
hasAttack
Indicates that one entity performs, possesses, or is associated with an attack directed toward another entity.
-
B.
hasCombatType
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
-
C.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.