Triple
T35941811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time and Time Again |
E1039465
|
entity |
| Predicate | workOfAuthorBestKnownFor |
P133557
|
FINISHED |
| Object | Lost Horizon |
—
|
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: Lost Horizon | Statement: [Time and Time Again, workOfAuthorBestKnownFor, Lost Horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOfAuthorBestKnownFor Context triple: [Time and Time Again, workOfAuthorBestKnownFor, Lost Horizon]
-
A.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
-
B.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
C.
authorIsKnownFor
Indicates that a particular author is widely recognized or notable for a specific work, genre, contribution, or characteristic.
-
D.
workByAuthorAlsoKnownFor
chosen
Indicates that a work is created by an author who is also notably recognized for another specified work or contribution.
-
E.
workOfAuthorWho
Indicates that one entity is a work (such as a book, article, or artwork) created by another entity who is its author.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.