Triple
T38147981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drak'Tharon Keep |
E952670
|
entity |
| Predicate | minLevelRequirement |
P65817
|
FINISHED |
| Object | 74 |
—
|
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: 74 | Statement: [Drak'Tharon Keep, minLevelRequirement, 74]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minLevelRequirement Context triple: [Drak'Tharon Keep, minLevelRequirement, 74]
-
A.
levelRequirement
Indicates that one entity specifies the minimum level or threshold another entity must meet in order for an action, access, or condition to be valid.
-
B.
minimumLevel
chosen
Indicates that one entity specifies the lowest allowable or required level, degree, or threshold at which another entity, condition, or action becomes valid or applicable.
-
C.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
D.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
E.
requiresMinimumScore
Indicates that one entity can only be obtained, accessed, or considered valid if another entity’s score meets or exceeds a specified minimum threshold.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.