Triple
T11620898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of the Hide |
E275633
|
entity |
| Predicate | targetUserLevel |
P100059
|
FINISHED |
| Object | professional players |
—
|
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: professional players | Statement: [Heart of the Hide, targetUserLevel, professional players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUserLevel Context triple: [Heart of the Hide, targetUserLevel, professional players]
-
A.
intendedPlayerLevel
chosen
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
B.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
C.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
D.
targetPerformanceLevel
Indicates the specific performance standard or level that an entity is expected or required to achieve.
-
E.
developmentLevel
Indicates the degree or stage of progress, advancement, or maturity that something has reached in its growth or evolution.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1206f1c81908d92024ef71958c0 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.