Triple
T29822751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grady Tripp |
E757288
|
entity |
| Predicate | hasWorkInProgress |
P56793
|
FINISHED |
| Object | unwieldy long novel |
—
|
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: unwieldy long novel | Statement: [Grady Tripp, hasWorkInProgress, unwieldy long novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInProgress Context triple: [Grady Tripp, hasWorkInProgress, unwieldy long novel]
-
A.
hasComponentWork
Indicates that one work includes another work as a constituent or subordinate component within it.
-
B.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
C.
hasWorkOn
chosen
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
D.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
E.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 5:30 p.m.