Triple
T12007098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP Regional |
E285807
|
entity |
| Predicate | serviceCategoryWithinCP |
P66133
|
FINISHED |
| Object | 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: Regional | Statement: [CP Regional, serviceCategoryWithinCP, Regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCategoryWithinCP Context triple: [CP Regional, serviceCategoryWithinCP, Regional]
-
A.
publicServiceCategory
chosen
Indicates the classification or type of public service that an entity, activity, or offering belongs to.
-
B.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
-
C.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
D.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c5cfc08190821e4b2940c51416 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.