Triple
T27860080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadow Lane (street) |
E704200
|
entity |
| Predicate | isCommonStreetNamePattern |
P165707
|
FINISHED |
| Object | English-speaking countries |
—
|
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: English-speaking countries | Statement: [Meadow Lane (street), isCommonStreetNamePattern, English-speaking countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonStreetNamePattern Context triple: [Meadow Lane (street), isCommonStreetNamePattern, English-speaking countries]
-
A.
isCommonStreetNameIn
chosen
Indicates that a given name is frequently used as a street name within a specified geographic area or jurisdiction.
-
B.
hasStreetNamingPattern
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
C.
hasNearbyStreetPattern
Indicates that one location has a street layout or configuration that is spatially close to, or in the vicinity of, another location’s street pattern.
-
D.
isCommonToponym
Indicates that a place name is widely used or shared by multiple distinct locations.
-
E.
hasStreetNameElement
Indicates that an address or location includes a specific street name component as part of its full designation.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 6:17 p.m.