Triple
T36574340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Kottke |
E902202
|
entity |
| Predicate | hasLongRunningProject |
P199945
|
FINISHED |
| Object | kottke.org |
—
|
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: kottke.org | Statement: [Jason Kottke, hasLongRunningProject, kottke.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongRunningProject Context triple: [Jason Kottke, hasLongRunningProject, kottke.org]
-
A.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
B.
hasPlannedProjects
Indicates that an entity is associated with projects that are intended or scheduled to be carried out in the future.
-
C.
hasLongRunningProgramming
Indicates that an entity is involved in or associated with programming activities that run or execute over an extended period of time.
-
D.
hasNotableProject
Indicates that an entity is associated with a project that is distinguished or recognized as significant in some way.
-
E.
hasPetProject
Indicates that an entity has a personal, often self-initiated project to which they are especially dedicated or attached.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: May 3, 2026, 4:11 p.m.