Triple
T9274782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supilinn district |
E222917
|
entity |
| Predicate | hasStreetNameTheme |
P36245
|
FINISHED |
| Object | food-related street names |
—
|
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: food-related street names | Statement: [Supilinn district, hasStreetNameTheme, food-related street names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetNameTheme Context triple: [Supilinn district, hasStreetNameTheme, food-related street names]
-
A.
hasStreetNamingPattern
chosen
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
B.
hasStreetNameElement
Indicates that an address or location includes a specific street name component as part of its full designation.
-
C.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
D.
hasStreetNamedAfter
Indicates that one entity has a street that is named in honor of or after another entity.
-
E.
hasNotableStreet
Indicates that an entity is associated with a particular street that is considered notable or significant.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078a045c8190b2c4d1ec64b932ad |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.