Triple
T30732446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Three Gables |
E782458
|
entity |
| Predicate | fictionalAddressType |
P3330
|
FINISHED |
| Object | suburban house |
—
|
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: suburban house | Statement: [The Adventure of the Three Gables, fictionalAddressType, suburban house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalAddressType Context triple: [The Adventure of the Three Gables, fictionalAddressType, suburban house]
-
A.
fictionalAddress
Indicates that an address associated with an entity is invented or not corresponding to a real-world location.
-
B.
typeOfAddress
Indicates the specific category or kind of address (e.g., home, work, billing) associated with an entity.
-
C.
addressType
chosen
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
D.
hasFictionalAddressTown
Indicates that an entity is associated with a town that serves as its fictional address location.
-
E.
fictionalResidence
Indicates that one entity is the place where another entity lives or is based within a fictional or imaginary context.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 29, 2026, 8:37 p.m.