Triple
T6336076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Testament |
E142493
|
entity |
| Predicate | hasAuthorAttribute |
P56172
|
FINISHED |
| Object | Holocaust survivor |
—
|
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: Holocaust survivor | Statement: [The Testament, hasAuthorAttribute, Holocaust survivor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorAttribute Context triple: [The Testament, hasAuthorAttribute, Holocaust survivor]
-
A.
hasAuthorField
Indicates that an entity includes a designated field or attribute for specifying its author.
-
B.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
C.
hasAuthorType
chosen
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
-
D.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
E.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.