Triple
T37662141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Jockey |
E937739
|
entity |
| Predicate | attackingEntity |
P2363
|
FINISHED |
| Object | baby zombie |
—
|
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: baby zombie | Statement: [Chicken Jockey, attackingEntity, baby zombie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackingEntity Context triple: [Chicken Jockey, attackingEntity, baby zombie]
-
A.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
B.
attackerSide
Indicates which party or faction is responsible for carrying out an attack in a conflict or violent incident.
-
C.
capturedAttacker
Indicates that an entity has successfully apprehended or taken control of an attacking entity.
-
D.
attacker
chosen
Indicates a relationship where one entity initiates a harmful or hostile action against another entity.
-
E.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:18 p.m.