Triple
T35185724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B.C. |
E1015978
|
entity |
| Predicate | authorUntil |
P195980
|
FINISHED |
| Object | Johnny Hart |
E1015986
|
NE 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: Johnny Hart | Statement: [B.C., authorUntil, Johnny Hart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorUntil Context triple: [B.C., authorUntil, Johnny Hart]
-
A.
authorPublished
Indicates that an author has published a particular work (such as a book, article, or paper).
-
B.
authorLaterBecame
Indicates that the subject, who is an author of something, subsequently took on or transitioned into the role or status specified by the object at a later time.
-
C.
authorFounded
Indicates that the author is the person who established or created the referenced organization, institution, or entity.
-
D.
authorOfPreviousWork
Indicates that one entity is the creator or writer of an earlier work referenced or built upon by another entity.
-
E.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
- F. None of above. chosen
Provenance (5 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803feaec88190a7ee000f03bd4397 |
completed | June 21, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.