Triple
T30407179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filecoin |
E773509
|
entity |
| Predicate | networkDesign |
P171586
|
FINISHED |
| Object | market-based storage pricing |
—
|
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: market-based storage pricing | Statement: [Filecoin, networkDesign, market-based storage pricing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkDesign Context triple: [Filecoin, networkDesign, market-based storage pricing]
-
A.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
B.
networkModel
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
-
C.
networkSection
Indicates that one entity represents a specific section, segment, or subdivision within a larger network structure.
-
D.
networkScale
Indicates the relative size, capacity, or extent of a network in terms of its reach or resources.
-
E.
netWork
Indicates a relationship where entities are connected or interact within a shared system, structure, or set of links that enables communication or 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:04 p.m.