Triple
T24165638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sword of Honour (TV serial) |
E598973
|
entity |
| Predicate | literarySourceNationality |
P36448
|
FINISHED |
| Object | British literature |
—
|
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: British literature | Statement: [Sword of Honour (TV serial), literarySourceNationality, British literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySourceNationality Context triple: [Sword of Honour (TV serial), literarySourceNationality, British literature]
-
A.
hasLiteraryOriginAuthorNationality
Indicates that the nationality of the author from whom a work or concept originates is being specified.
-
B.
literaryOriginCountry
chosen
Indicates the country from which a literary work or literary tradition originally comes.
-
C.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
D.
authorNationality
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
E.
literaryAuthor
Indicates that one entity is the author or writer of a literary work represented by the other 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.