Triple
T31959049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Future of Politics |
E815983
|
entity |
| Predicate | hasNotablePersonAsAuthor |
P7039
|
FINISHED |
| Object | Charles Kennedy |
—
|
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: Charles Kennedy | Statement: [The Future of Politics, hasNotablePersonAsAuthor, Charles Kennedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePersonAsAuthor Context triple: [The Future of Politics, hasNotablePersonAsAuthor, Charles Kennedy]
-
A.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
B.
hasNotableWriter
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
-
C.
notableAuthorPublished
chosen
Indicates that a work was published by an author who is recognized as notable or distinguished.
-
D.
notableAuthorAttribute
Indicates that a particular attribute or characteristic is especially notable or significant for an author in the context of their work or recognition.
-
E.
authorIsKnownFor
Indicates that a particular author is widely recognized or notable for a specific work, genre, contribution, or characteristic.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
Created at: May 1, 2026, 12:08 a.m.