Triple
T30407183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filecoin |
E773509
|
entity |
| Predicate | whitepaperURL |
P30417
|
FINISHED |
| Object | https://filecoin.io/filecoin.pdf |
—
|
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: https://filecoin.io/filecoin.pdf | Statement: [Filecoin, whitepaperURL, https://filecoin.io/filecoin.pdf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whitepaperURL Context triple: [Filecoin, whitepaperURL, https://filecoin.io/filecoin.pdf]
-
A.
publishedWhitePaperOn
chosen
Indicates that an entity has authored and released a formal white paper on a specified topic or subject.
-
B.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
C.
dataPublication
Indicates that some data has been made publicly available or formally released, typically through a defined dissemination or publishing process.
-
D.
publicDocument
Indicates that a document is officially available to the general public without access restrictions.
-
E.
DOC
Indicates that one entity is a document associated with, produced by, or describing another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:04 p.m.