Triple
T20983406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrine of Secrets |
E516825
|
entity |
| Predicate | hasSelectionSize |
P142356
|
FINISHED |
| Object | four perks per rotation |
—
|
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: four perks per rotation | Statement: [Shrine of Secrets, hasSelectionSize, four perks per rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelectionSize Context triple: [Shrine of Secrets, hasSelectionSize, four perks per rotation]
-
A.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
B.
hasSelectionUnit
Indicates that an entity is associated with a specific unit or mechanism used to make a selection among available options.
-
C.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
D.
hasMemberSelectionMethod
Indicates the method or criteria by which members of a group, organization, or body are chosen or selected.
-
E.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe1474c8190912b90da0973f99f |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:48 p.m.