Triple
T36594083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEM |
E902747
|
entity |
| Predicate | honourJurisdiction |
P145220
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [BEM, honourJurisdiction, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honourJurisdiction Context triple: [BEM, honourJurisdiction, United Kingdom]
-
A.
honorsJurisdiction
chosen
Indicates that one entity recognizes and respects the legal authority, rules, or governance of another jurisdiction.
-
B.
nobleJurisdiction
Indicates that an entity holds legal or administrative authority associated with nobility over a certain domain or group.
-
C.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
D.
heldForJurisdiction
Indicates that an entity is being detained or kept in custody specifically for legal or jurisdictional reasons by a particular authority.
-
E.
canonicalJurisdictionOf
Indicates that one entity holds official legal or ecclesiastical authority over another entity or domain as its recognized jurisdiction.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.