Triple
T9029616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darknodes |
E216134
|
entity |
| Predicate | mustMaintain |
P37638
|
FINISHED |
| Object | online availability |
—
|
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 availability | Statement: [Darknodes, mustMaintain, online availability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustMaintain Context triple: [Darknodes, mustMaintain, online availability]
-
A.
mustRetain
Indicates that an entity is required to keep or preserve another entity and is not allowed to discard, delete, or release it.
-
B.
soughtToMaintain
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
-
C.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
D.
mustRespect
Indicates that one entity is obligated to show respect or deference toward another entity.
-
E.
maintenanceRequirement
chosen
Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
- 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_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. |
Created at: March 30, 2026, 7:08 p.m.