Triple
T35413474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Plaza |
E1023572
|
entity |
| Predicate | hasPathwayPattern |
P8151
|
FINISHED |
| Object | hub-and-spoke design |
—
|
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: hub-and-spoke design | Statement: [Central Plaza, hasPathwayPattern, hub-and-spoke design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPathwayPattern Context triple: [Central Plaza, hasPathwayPattern, hub-and-spoke design]
-
A.
hasPathway
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
B.
hasSubPathway
Indicates that one pathway is a component or subordinate segment of a larger, encompassing pathway.
-
C.
includesPathwaysFor
Indicates that one entity contains or provides designated routes, channels, or mechanisms that enable movement, flow, or progression for another entity or process.
-
D.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
E.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 3, 2026, 4:03 p.m.