Triple
T6912193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alphabet Streets |
E159963
|
entity |
| Predicate | streetNamingPattern |
P36245
|
FINISHED |
| Object | alphabetical order |
—
|
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: alphabetical order | Statement: [The Alphabet Streets, streetNamingPattern, alphabetical order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNamingPattern Context triple: [The Alphabet Streets, streetNamingPattern, alphabetical order]
-
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.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
D.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
E.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c2e79881909eeb061be0a72bdf |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.