Triple
T5402169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prove Thyself |
E120801
|
entity |
| Predicate | perkSlotType |
P30799
|
FINISHED |
| Object | Standard survivor perk slot |
—
|
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: Standard survivor perk slot | Statement: [Prove Thyself, perkSlotType, Standard survivor perk slot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perkSlotType Context triple: [Prove Thyself, perkSlotType, Standard survivor perk slot]
-
A.
perkType
Indicates the specific category or kind of benefit, bonus, or advantage associated with an entity or situation.
-
B.
slotType
chosen
Indicates the classification or category assigned to a particular slot or position within a structure, system, or sequence.
-
C.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
-
D.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
E.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.