Triple
T19310916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Points (Jacksonville) |
E482963
|
entity |
| Predicate | streetPatternNamedFor |
P135540
|
FINISHED |
| Object | five-way intersection |
—
|
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: five-way intersection | Statement: [Five Points (Jacksonville), streetPatternNamedFor, five-way intersection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetPatternNamedFor Context triple: [Five Points (Jacksonville), streetPatternNamedFor, five-way intersection]
-
A.
hasStreetNamingPattern
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
B.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
C.
namedAfterStreet
Indicates that an entity’s name is derived from or taken in honor of a particular street.
-
D.
hasStreetNickname
Indicates that an entity is known by a particular informal or colloquial name used on the street or in everyday speech.
-
E.
hasStreetNameLanguage
Indicates that the language in which a street name is expressed is specified.
- F. None of above. chosen
Provenance (4 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cd270c819094fd2faa0681d2ad |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.