Triple
T34368246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blifil |
E882078
|
entity |
| Predicate | nationalityOfWorkAuthor |
P91127
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Blifil, nationalityOfWorkAuthor, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityOfWorkAuthor Context triple: [Blifil, nationalityOfWorkAuthor, English]
-
A.
authorNationality
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
B.
sourceWorkNationality
chosen
Indicates that a work or source is associated with a particular nationality or country of origin.
-
C.
appearsInWorkByAuthorNationality
Indicates that an entity appears in a work created by an author of a specified nationality.
-
D.
countryOfNotableWork
Indicates the country with which a notable work is primarily associated, such as where it was created, set, or gained its significance.
-
E.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:58 a.m.