Triple
T730382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire and the Humber |
E14816
|
entity |
| Predicate | createdAsRegion |
P18356
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Yorkshire and the Humber, createdAsRegion, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsRegion Context triple: [Yorkshire and the Humber, createdAsRegion, 1994]
-
A.
emergedInRegion
Indicates that something first appeared, originated, or came into existence within a specified geographic region.
-
B.
createdForJurisdiction
chosen
Indicates that something was created specifically to apply within, serve, or be used by a particular legal or geographic jurisdiction.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
createdRegimeOf
Indicates that one entity brought about, established, or was responsible for the formation of a particular regime or system of rule for another entity.
-
E.
formsNaturalRegionWith
Indicates that two or more geographic entities together constitute or belong to the same continuous natural region or landscape unit.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f9b7608190bf97c8418a26e632 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.