Triple
T4481162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East-West Tollway corridor |
E100136
|
entity |
| Predicate | majorCenterFor |
P164
|
FINISHED |
| Object | business services |
—
|
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: business services | Statement: [East-West Tollway corridor, majorCenterFor, business services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCenterFor Context triple: [East-West Tollway corridor, majorCenterFor, business services]
-
A.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
B.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
C.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
D.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
E.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:36 p.m.