Triple
T30360428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Business District of Seattle |
E772266
|
entity |
| Predicate | isPrimaryDowntownCoreOf |
P16032
|
FINISHED |
| Object | Seattle |
—
|
NE NERFINISHED |
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: Seattle | Statement: [Central Business District of Seattle, isPrimaryDowntownCoreOf, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryDowntownCoreOf Context triple: [Central Business District of Seattle, isPrimaryDowntownCoreOf, Seattle]
-
A.
isDowntownCoreOf
chosen
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
B.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
-
C.
isPrimaryCommercialAreaOf
Indicates that one area serves as the main center of commercial activity for another specified place or region.
-
D.
isTownCenterOf
Indicates that a location functions as the central, primary area or hub of a specified town.
-
E.
isDowntownHub
Indicates that a location functions as a central, primary hub within a city’s downtown area.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 7:57 p.m.