Triple
T11777292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogarth House |
E280049
|
entity |
| Predicate | inceptionAsLiterarySite |
P85173
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Hogarth House, inceptionAsLiterarySite, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsLiterarySite Context triple: [Hogarth House, inceptionAsLiterarySite, early 20th century]
-
A.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
B.
literaryCenter
chosen
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
-
C.
inLiterature
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
D.
literaryThemeInvolvement
Indicates the involvement or presence of a particular literary theme within a work, passage, or character arc.
-
E.
literaryInfluence
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.