Triple
T17435028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fortunate Pilgrim |
E423978
|
entity |
| Predicate | describedAsByAuthor |
P976
|
FINISHED |
| Object | Mario Puzo's best work |
—
|
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: Mario Puzo's best work | Statement: [The Fortunate Pilgrim, describedAsByAuthor, Mario Puzo's best work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsByAuthor Context triple: [The Fortunate Pilgrim, describedAsByAuthor, Mario Puzo's best work]
-
A.
describedByAuthorAs
chosen
Indicates that one entity is characterized, labeled, or portrayed in a particular way by an author.
-
B.
authorDescribedIn
Indicates that information about an author is provided or discussed within a particular document or source.
-
C.
authorsDescribedBy
Indicates that an entity serves as a descriptive account or characterization of one or more authors.
-
D.
authorOfDescription
Indicates that an entity is the creator or writer of a particular description or explanatory text about something.
-
E.
authorDescription
Indicates that a person provides a textual description or biographical summary of an 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4490361c081908fd24f9a812f212c |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.