Triple
T17395519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Content Collection 2 |
E422942
|
entity |
| Predicate | isExpansionForMode |
P127316
|
FINISHED |
| Object | online multiplayer |
—
|
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: online multiplayer | Statement: [Content Collection 2, isExpansionForMode, online multiplayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpansionForMode Context triple: [Content Collection 2, isExpansionForMode, online multiplayer]
-
A.
hasExpansionType
Indicates that an entity is associated with a particular mode or category of expansion (such as how it grows, extends, or scales).
-
B.
hasExpansionModel
Indicates that one entity is associated with a specific model or schema used to define how it can be expanded, detailed, or elaborated.
-
C.
hasExpansionInterface
Indicates that an entity provides or supports an interface through which it can be expanded or extended with additional components or functionality.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
hasExpansionName
Indicates that an entity has a specific name used for its expanded or extended form.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abcd8b081908579ee9a80f65802 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.