Triple
T27426696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Bonhomme |
E690505
|
entity |
| Predicate | hasCoAuthored |
P2389
|
FINISHED |
| Object | book "Red Bull Air Race: The Inside Track" |
—
|
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: book "Red Bull Air Race: The Inside Track" | Statement: [Paul Bonhomme, hasCoAuthored, book "Red Bull Air Race: The Inside Track"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoAuthored Context triple: [Paul Bonhomme, hasCoAuthored, book "Red Bull Air Race: The Inside Track"]
-
A.
hasCoauthor
chosen
Indicates that two or more entities have jointly authored the same work or publication.
-
B.
hasChildCoauthor
Indicates that an entity has at least one child who is also a coauthor with that entity on a work or publication.
-
C.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
D.
hasCoauthorBackground
Indicates that two or more coauthors share a specified background, such as educational, professional, cultural, or experiential context.
-
E.
authoredWith
Indicates that two or more entities jointly created or wrote a work together.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: April 27, 2026, 12:41 p.m.