Triple
T10920270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Bishop |
E257927
|
entity |
| Predicate | weaponInspiration |
P96650
|
FINISHED |
| Object | Mockingbird’s battle staves |
—
|
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: Mockingbird’s battle staves | Statement: [Kate Bishop, weaponInspiration, Mockingbird’s battle staves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponInspiration Context triple: [Kate Bishop, weaponInspiration, Mockingbird’s battle staves]
-
A.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
B.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
C.
weaponDiscipline
Indicates that an entity practices, adheres to, or is governed by a particular system, style, or code of weapon use or combat training.
-
D.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
E.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77081a0c48190b7aa4a482032d1ea |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:22 p.m.