Triple
T34653137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Road to Understanding |
E889894
|
entity |
| Predicate | hasAuthorOfRelatedWork |
P154273
|
FINISHED |
| Object | Pollyanna |
—
|
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: Pollyanna | Statement: [The Road to Understanding, hasAuthorOfRelatedWork, Pollyanna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorOfRelatedWork Context triple: [The Road to Understanding, hasAuthorOfRelatedWork, Pollyanna]
-
A.
hasAuthorOfOtherWork
chosen
Indicates that an entity is the author of another distinct work associated with the first entity.
-
B.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
C.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
D.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
E.
hasAuthorOfKeyWork
Indicates that an entity serves as the author or creator of a significant or primary work associated with another entity.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 2:04 a.m.