Triple
T11656809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazaa |
E277029
|
entity |
| Predicate | usesNetworkModel |
P56711
|
FINISHED |
| Object | decentralized peer-to-peer network |
—
|
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: decentralized peer-to-peer network | Statement: [Kazaa, usesNetworkModel, decentralized peer-to-peer network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNetworkModel Context triple: [Kazaa, usesNetworkModel, decentralized peer-to-peer network]
-
A.
supportsNetworkingModel
Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
-
B.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
C.
basedOnNetwork
Indicates that something is determined, derived, or operates according to a particular network or network-related characteristics.
-
D.
networkModel
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
-
E.
usesTargetNetwork
chosen
Indicates that an entity operates or communicates through a specified target network as its underlying connection or infrastructure.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.