Triple
T24763624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Loom of Youth |
E619518
|
entity |
| Predicate | hasAuthorSiblingRelation |
P86555
|
FINISHED |
| Object | Evelyn Waugh |
—
|
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: Evelyn Waugh | Statement: [The Loom of Youth, hasAuthorSiblingRelation, Evelyn Waugh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorSiblingRelation Context triple: [The Loom of Youth, hasAuthorSiblingRelation, Evelyn Waugh]
-
A.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
B.
hasSiblingAuthors
chosen
Indicates that two or more authors share at least one parent, i.e., they are siblings who have both authored works.
-
C.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
D.
hasChildCoauthor
Indicates that an entity has at least one child who is also a coauthor with that entity on a work or publication.
-
E.
hasCreatorRelationshipToSubject
Indicates that an entity stands in a creator role with respect to the subject, meaning it is responsible for bringing the subject into existence or producing it.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a330f0819081bc60b9275d883d |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:28 a.m.