Triple
T27750422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Windows games |
E702098
|
entity |
| Predicate | supportsModding |
P201488
|
FINISHED |
| Object | many titles |
—
|
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: many titles | Statement: [Microsoft Windows games, supportsModding, many titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsModding Context triple: [Microsoft Windows games, supportsModding, many titles]
-
A.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
B.
hasMod
Indicates that one element functions as a modifier that semantically or syntactically qualifies, restricts, or elaborates another element.
-
C.
isModular
Indicates that something is composed of distinct, interchangeable parts or units that can be independently created, modified, or replaced within a larger whole.
-
D.
supportsModelingOf
Indicates that one entity provides the capability or functionality needed to represent, simulate, or model another entity or process.
-
E.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: April 27, 2026, 4:19 p.m.