Triple
T2438340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Street Historic District |
E53214
|
entity |
| Predicate | hasStreetscapeType |
P6822
|
FINISHED |
| Object | small-town main 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: small-town main street | Statement: [Church Street Historic District, hasStreetscapeType, small-town main street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetscapeType Context triple: [Church Street Historic District, hasStreetscapeType, small-town main street]
-
A.
hasTreeLinedStreets
Indicates that the streets in a given area are lined or bordered with trees along their sides.
-
B.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
D.
hasScenicValue
Indicates that something possesses notable aesthetic or visual appeal, often due to its natural beauty or pleasing surroundings.
-
E.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.