Triple
T37460294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grobbulus |
E930899
|
entity |
| Predicate | bossCategory |
P87
|
FINISHED |
| Object | Construct Quarter abomination boss |
—
|
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: Construct Quarter abomination boss | Statement: [Grobbulus, bossCategory, Construct Quarter abomination boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossCategory Context triple: [Grobbulus, bossCategory, Construct Quarter abomination boss]
-
A.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
B.
cornerCategory
Indicates that something is classified as belonging to a specific type or category of corner.
-
C.
unitCategory
Indicates the classification or type of unit that an entity belongs to within a defined system or context.
-
D.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
commandCategory
Indicates that an action or command is classified into a specific category or type based on its function or purpose.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.