Triple
T30419897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary Troup |
E773871
|
entity |
| Predicate | appearsAsAuthorOf |
P114493
|
FINISHED |
| Object | Bad Twin manuscript in Lost |
—
|
LITERAL 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: Bad Twin manuscript in Lost | Statement: [Gary Troup, appearsAsAuthorOf, Bad Twin manuscript in Lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsAuthorOf Context triple: [Gary Troup, appearsAsAuthorOf, Bad Twin manuscript in Lost]
-
A.
workAppearedInAuthor
Indicates that a particular work by an author appeared in or was included within another creator’s authored work (e.g., as a contribution, feature, or inclusion).
-
B.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
-
C.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
-
D.
hasAuthorOfKeyWork
chosen
Indicates that an entity serves as the author or creator of a significant or primary work associated with another entity.
-
E.
workAuthoredIn
Indicates that a work was created or written in a particular place or time context.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 8:05 p.m.