Triple
T37664671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zombie Piglin |
E937793
|
entity |
| Predicate | isNeutralTo |
P162774
|
FINISHED |
| Object | player wearing no gold armor |
—
|
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 wearing no gold armor | Statement: [Zombie Piglin, isNeutralTo, player wearing no gold armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNeutralTo Context triple: [Zombie Piglin, isNeutralTo, player wearing no gold armor]
-
A.
isNeutral
Indicates that an entity maintains a balanced, unbiased, or non-aligned stance with respect to other entities, options, or conflicting sides.
-
B.
isNeutralRelativeTo
chosen
Indicates that one entity maintains a neutral, non-favoring stance or position with respect to another entity.
-
C.
isNeutralAbout
Indicates that one entity has no strong positive or negative opinion, preference, or stance toward another entity or subject.
-
D.
isNeutralOn
Indicates a stance of neither support nor opposition toward a subject, remaining impartial or undecided.
-
E.
isNeutralUnder
Indicates that one entity does not affect, alter, or interact with another in a way that changes its state, value, 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.