Triple
T36396077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portlaoise |
E896483
|
entity |
| Predicate | isRegionalCommercialCentreFor |
P117896
|
FINISHED |
| Object | County Laois |
—
|
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: County Laois | Statement: [Portlaoise, isRegionalCommercialCentreFor, County Laois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalCommercialCentreFor Context triple: [Portlaoise, isRegionalCommercialCentreFor, County Laois]
-
A.
hasCommercialCenterType
Indicates that an entity has or is associated with a specific type or category of commercial center (e.g., mall, shopping district, business park).
-
B.
servesAsRegionalCenterFor
chosen
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
C.
hasMajorCommercialCentre
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
D.
hasRegionalCentresIn
Indicates that an entity maintains one or more regional centers located in the specified place or area.
-
E.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.