Triple
T9029625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darknodes |
E216134
|
entity |
| Predicate | abstractsFromUsers |
P85767
|
FINISHED |
| Object | complexity of cross-chain interactions |
—
|
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: complexity of cross-chain interactions | Statement: [Darknodes, abstractsFromUsers, complexity of cross-chain interactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstractsFromUsers Context triple: [Darknodes, abstractsFromUsers, complexity of cross-chain interactions]
-
A.
abstracts
Indicates that one entity generalizes, conceptualizes, or derives an abstract representation from another entity or set of details.
-
B.
writtenPapers
Indicates that an entity has authored or co-authored one or more academic or written papers.
-
C.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
D.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another entity.
-
E.
abridgedIn
Indicates that one entity is a shortened or condensed version of the content found within another entity.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.