Triple
T24983736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon of York |
E625243
|
entity |
| Predicate | withinProvince |
P20236
|
FINISHED |
| Object | Province of York |
E18677
|
NE 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: Province of York | Statement: [Canon of York, withinProvince, Province of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinProvince Context triple: [Canon of York, withinProvince, Province of York]
-
A.
heldInProvince
Indicates that an event or activity takes place within the boundaries of a specified province.
-
B.
isInProvince
chosen
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
C.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
D.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
-
E.
protectedProvince
Indicates that a province is under protection or safeguarding by another entity or authority.
- F. None of above.
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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a103363c2c08190a64ee4f8dff65090 |
completed | May 22, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:02 a.m.