Triple
T34797629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunmer |
E1003132
|
entity |
| Predicate | typicalClassStrength |
P99997
|
FINISHED |
| Object | battlemage |
—
|
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: battlemage | Statement: [Dunmer, typicalClassStrength, battlemage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClassStrength Context triple: [Dunmer, typicalClassStrength, battlemage]
-
A.
typicalClassSize
Indicates the usual or average number of students (or participants) that are present in a single class or course section.
-
B.
classStrength
chosen
Indicates the relative power, influence, or effectiveness associated with a particular class or category in a given context.
-
C.
typicalEnrollment
Indicates the usual or standard number of participants or members enrolled in something, such as a course, program, or institution.
-
D.
typicalClassYear
Indicates the usual or expected academic year level associated with an entity, such as when a course is typically taken or a program is normally completed.
-
E.
typicalDegree
Indicates the usual or characteristic level, intensity, or extent to which something holds or applies in a given context.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.