Triple
T37769169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piglin Brute |
E941493
|
entity |
| Predicate | guardsStructure |
P166513
|
FINISHED |
| Object | bastion remnants |
—
|
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: bastion remnants | Statement: [Piglin Brute, guardsStructure, bastion remnants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardsStructure Context triple: [Piglin Brute, guardsStructure, bastion remnants]
-
A.
gateStructure
Indicates that one entity functions as a gate or gateway structure associated with, controlling access to, or forming part of another entity.
-
B.
guardedStructure
chosen
Indicates that a structure is being protected or watched over by a guarding entity or mechanism.
-
C.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
D.
guardFeature
Indicates that one entity protects, secures, or restricts access to a particular feature of another entity.
-
E.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
- 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_69fbaf1c5a588190b213d1a22511e298 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.