Triple
T37769211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piglin Brute |
E941493
|
entity |
| Predicate | languageKey |
P203606
|
FINISHED |
| Object | entity.minecraft.piglin_brute |
—
|
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: entity.minecraft.piglin_brute | Statement: [Piglin Brute, languageKey, entity.minecraft.piglin_brute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageKey Context triple: [Piglin Brute, languageKey, entity.minecraft.piglin_brute]
-
A.
languageOfKeyText
Indicates that a specified language is the primary language in which a given key or central text is written.
-
B.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
C.
languageOfLocalization
Indicates the language into which something (such as software, content, or an interface) has been localized for use or display.
-
D.
languageGroupName
Indicates the name assigned to a particular language group or linguistic classification.
-
E.
languageLabel
Indicates the human-readable name or label of a language associated with an entity or resource.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_6a01b240fd1c81908fbc7c0fd248723d |
completed | May 11, 2026, 10:41 a.m. |
Created at: May 3, 2026, 4:19 p.m.