Triple
T37293713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Street (Trench Town) |
E925738
|
entity |
| Predicate | streetNameType |
P44319
|
FINISHED |
| Object | numbered street name |
—
|
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: numbered street name | Statement: [Third Street (Trench Town), streetNameType, numbered street name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNameType Context triple: [Third Street (Trench Town), streetNameType, numbered street name]
-
A.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
B.
streetOrAreaType
chosen
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
C.
streetPatternNamedFor
Indicates that a street pattern or layout is named in honor of, or derived from, a particular entity.
-
D.
streetOrArea
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
E.
namedAfterStreet
Indicates that an entity’s name is derived from or taken in honor of a particular street.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.