Triple
T554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Nelson |
E10
|
entity |
| Predicate | theorized |
P119
|
FINISHED |
| Object | non-linear, interconnected digital documents |
—
|
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: non-linear, interconnected digital documents | Statement: [Ted Nelson, theorized, non-linear, interconnected digital documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theorized Context triple: [Ted Nelson, theorized, non-linear, interconnected digital documents]
-
A.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
B.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69a22735e1b081908bd0457057dcf086 |
completed | Feb. 27, 2026, 11:22 p.m. |
| NER | Named-entity recognition | batch_69a2304aaa2c8190ab7e8dd5da977c11 |
completed | Feb. 28, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69a22918087081909e717b8bee896e8f |
completed | Feb. 27, 2026, 11:30 p.m. |
| PDg | Predicate description generation | batch_69a23049fde881908c53b5d18ebc73d0 |
completed | Feb. 28, 2026, 12:01 a.m. |
Created at: Feb. 27, 2026, 11:24 p.m.