Triple
T27559985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Gruber |
E695744
|
entity |
| Predicate | startOfWorkOn |
P30363
|
FINISHED |
| Object | Daring Fireball (2002) |
—
|
NE NERFINISHED |
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: Daring Fireball (2002) | Statement: [John Gruber, startOfWorkOn, Daring Fireball (2002)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfWorkOn Context triple: [John Gruber, startOfWorkOn, Daring Fireball (2002)]
-
A.
startOfWork
Indicates the point in time or event at which a work activity, project, or task begins.
-
B.
workOn
chosen
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
collaborationStartWork
Indicates the point in time when a collaborative effort between entities begins or is initiated.
-
D.
namedForWorkOn
Indicates that an entity is named in honor of another entity specifically because of that entity’s work or contributions in a particular field or endeavor.
-
E.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 1:38 p.m.