Triple
T37458301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aggro Shaman |
E930853
|
entity |
| Predicate | requiresFormat |
P83073
|
FINISHED |
| Object | Constructed |
—
|
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: Constructed | Statement: [Aggro Shaman, requiresFormat, Constructed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFormat Context triple: [Aggro Shaman, requiresFormat, Constructed]
-
A.
formatRequirement
chosen
Indicates that one entity specifies the required structure, style, or arrangement that another entity must follow or conform to.
-
B.
containsFormat
Indicates that one entity includes or is associated with a particular format type as part of its content or representation.
-
C.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
D.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
-
E.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
- 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_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: May 3, 2026, 4:17 p.m.