Triple
T37769182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piglin Brute |
E941493
|
entity |
| Predicate | attacksOnSight |
P34832
|
FINISHED |
| Object | player |
—
|
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: player | Statement: [Piglin Brute, attacksOnSight, player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attacksOnSight Context triple: [Piglin Brute, attacksOnSight, player]
-
A.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
B.
cyberAspect
Indicates a relationship where an entity possesses, involves, or is characterized by a particular cybersecurity-related feature, property, or dimension.
-
C.
attacks
chosen
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
D.
facesThreat
Indicates that an entity is exposed to or confronted by a potential danger, risk, or harmful situation.
-
E.
securityReputation
Indicates the assessed trustworthiness or risk level associated with an entity’s security posture or behavior.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:19 p.m.