Triple
T37551068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | lockoutType |
P188258
|
FINISHED |
| Object | separate 10-player and 25-player lockouts |
—
|
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: separate 10-player and 25-player lockouts | Statement: [Trial of the Crusader, lockoutType, separate 10-player and 25-player lockouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockoutType Context triple: [Trial of the Crusader, lockoutType, separate 10-player and 25-player lockouts]
-
A.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
B.
supportsLockoutType
Indicates that one entity is compatible with or able to operate using a specified lockout type.
-
C.
typeOfLock
Indicates the specific kind or category of lock mechanism associated with an entity.
-
D.
lockConfiguration
Indicates that one entity sets, defines, or controls the locking behavior or settings applied to another entity.
-
E.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.