Triple
T22995102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest Regional |
E572166
|
entity |
| Predicate | isOneOfRegionalBrackets |
P150555
|
FINISHED |
| Object | East Regional |
—
|
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: East Regional | Statement: [Southwest Regional, isOneOfRegionalBrackets, East Regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfRegionalBrackets Context triple: [Southwest Regional, isOneOfRegionalBrackets, East Regional]
-
A.
hasRegionalAffiliation
Indicates that an entity is associated with, belongs to, or is officially linked to a specific geographic region.
-
B.
isFromRegion
Indicates that one entity originates from, is associated with, or belongs to a specified geographic region.
-
C.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
D.
isRegionalDestination
Indicates that a place serves as a primary travel or attraction target within a specific geographic region.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f25af48190a98b7baeec824ae6 |
completed | April 29, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.