Triple
T24436878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Mitchell |
E616146
|
entity |
| Predicate | coauthoredWork |
P2389
|
FINISHED |
| Object | Loving What Is |
—
|
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: Loving What Is | Statement: [Stephen Mitchell, coauthoredWork, Loving What Is]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coauthoredWork Context triple: [Stephen Mitchell, coauthoredWork, Loving What Is]
-
A.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
B.
hasCoauthor
chosen
Indicates that two or more entities have jointly authored the same work or publication.
-
C.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
-
D.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
E.
coPublicationWith
Indicates a relationship where two or more entities have jointly authored and published the same work.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29786fbcc819090a04bf62c03e9a1 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.