Triple
T16264587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Avenue (Seattle) |
E394840
|
entity |
| Predicate | nameFormat |
P60600
|
FINISHED |
| Object | numbered avenue |
—
|
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 avenue | Statement: [5th Avenue (Seattle), nameFormat, numbered avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameFormat Context triple: [5th Avenue (Seattle), nameFormat, numbered avenue]
-
A.
nameStyle
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
B.
olsonFormatName
Indicates a formatting relationship where a name is converted into or represented in the specific style or convention defined by the Olson format.
-
C.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
D.
namePattern
chosen
Indicates that an entity’s name follows or matches a specified pattern or format.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c73944819085633e6d2a69bae9 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.