Triple
T12621639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quake Champions |
E301392
|
entity |
| Predicate | networkMode |
P105957
|
FINISHED |
| Object | online only |
—
|
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 only | Statement: [Quake Champions, networkMode, online only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkMode Context triple: [Quake Champions, networkMode, online only]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
networkModel
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
-
C.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
D.
networkingOptions
Indicates the available ways entities can establish, configure, or use network connections or communication channels between them.
-
E.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96179c7648190a05a13991d62bebb |
completed | April 10, 2026, 8:45 p.m. |
Created at: April 9, 2026, 5:14 p.m.