Triple
T37462028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun Warrior |
E930940
|
entity |
| Predicate | classStrengthUtilized |
P190724
|
FINISHED |
| Object | armor gain |
—
|
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: armor gain | Statement: [C’Thun Warrior, classStrengthUtilized, armor gain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classStrengthUtilized Context triple: [C’Thun Warrior, classStrengthUtilized, armor gain]
-
A.
classStrength
Indicates the relative power, influence, or effectiveness associated with a particular class or category in a given context.
-
B.
classLength
Indicates the duration or length of time that a class session lasts.
-
C.
participantStrength
Indicates the degree or level of involvement, influence, or contribution that a participant has within a given event, interaction, or relationship.
-
D.
availableStrength
Indicates the amount of strength or power that an entity currently has ready for use or deployment.
-
E.
numberWithinClass
Indicates that an entity has a specific numerical value or position that is defined relative to a particular class or category it belongs to.
- F. None of above. chosen
Provenance (4 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_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.