Triple
T36990301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madison–Putnam–60th Place Historic District |
E915076
|
entity |
| Predicate | streetIncluded |
P127309
|
FINISHED |
| Object | Madison Street |
—
|
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: Madison Street | Statement: [Madison–Putnam–60th Place Historic District, streetIncluded, Madison Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetIncluded Context triple: [Madison–Putnam–60th Place Historic District, streetIncluded, Madison Street]
-
A.
streetNetworkIncludes
Indicates that a given street network contains or encompasses a specified street segment, feature, or component as part of its structure.
-
B.
townIncluded
Indicates that one town is geographically or administratively contained within another specified area or jurisdiction.
-
C.
streetOrArea
chosen
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
D.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
E.
streetFunction
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.