Triple
T37508657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soulrender Dormazain |
E932160
|
entity |
| Predicate | encounterSize |
P83535
|
FINISHED |
| Object | 10-player |
—
|
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: 10-player | Statement: [Soulrender Dormazain, encounterSize, 10-player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterSize Context triple: [Soulrender Dormazain, encounterSize, 10-player]
-
A.
encounterFrequency
Indicates how often two entities come into contact or interact with each other over a given period.
-
B.
encounterStyle
Indicates the manner or format in which two or more entities meet, interact, or come into contact with each other.
-
C.
ensembleSize
chosen
Indicates the number of individual members or participants that make up a given group or ensemble.
-
D.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
E.
L5Encounter
Indicates an interaction or meeting occurs between entities at level or context L5.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.