Triple
T23132137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academy Street Historic District |
E577198
|
entity |
| Predicate | hasCoreStreet |
P461
|
FINISHED |
| Object | Academy 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: Academy Street | Statement: [Academy Street Historic District, hasCoreStreet, Academy Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreStreet Context triple: [Academy Street Historic District, hasCoreStreet, Academy Street]
-
A.
hasCentralStreet
Indicates that a place or area possesses a primary or main street that serves as its central thoroughfare.
-
B.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
C.
hasMainStreet
chosen
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
-
D.
hasCoreTown
Indicates that an entity possesses or is associated with a primary or central town that serves as its main urban center.
-
E.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e88909881908c695cd7d39d380c |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.