Triple
T37471066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skoldus Hall |
E931152
|
entity |
| Predicate | supportsPlayerSize |
P83507
|
FINISHED |
| Object | solo |
—
|
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: solo | Statement: [Skoldus Hall, supportsPlayerSize, solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayerSize Context triple: [Skoldus Hall, supportsPlayerSize, solo]
-
A.
supportsPlayer
Indicates that one entity provides assistance, resources, or backing to a player in achieving their goals or performing actions.
-
B.
supportsMediaSize
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified media size.
-
C.
supportsPlayers
chosen
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
D.
hasPlaySurfaceDimensions
Indicates the specific measurements or size characteristics that define the dimensions of a play surface.
-
E.
spriteSizeSupport
Indicates that an entity supports handling or displaying sprites at specific sizes or resolutions.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.