Triple
T17031413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cunningham family home |
E413205
|
entity |
| Predicate | fictionalStreetType |
P44319
|
FINISHED |
| Object | residential suburban street |
—
|
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: residential suburban street | Statement: [Cunningham family home, fictionalStreetType, residential suburban street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalStreetType Context triple: [Cunningham family home, fictionalStreetType, residential suburban street]
-
A.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
B.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
C.
fictionalAddress
Indicates that an address associated with an entity is invented or not corresponding to a real-world location.
-
D.
streetOrAreaType
chosen
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
E.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d9e7d481909d3d5bd241bd68f1 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.