Triple
T31670734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumberland Fusiliers |
E808261
|
entity |
| Predicate | receivedRoyalTitleFrom |
P33027
|
FINISHED |
| Object | King George V |
—
|
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: King George V | Statement: [Northumberland Fusiliers, receivedRoyalTitleFrom, King George V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedRoyalTitleFrom Context triple: [Northumberland Fusiliers, receivedRoyalTitleFrom, King George V]
-
A.
nobleTitleGranted
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
-
B.
dateGrantedTitleRoyal
Indicates the specific date on which a royal title was formally granted to an entity.
-
C.
nobleTitleAcquiredThrough
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
-
D.
monarchWhoGrantedTitle
chosen
Indicates the monarch who conferred or bestowed a particular title upon an individual.
-
E.
associatedTitleAfterEnthronement
Indicates the formal title or designation that is linked to an individual specifically after they have been enthroned or installed in an official position.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 30, 2026, 11:01 p.m.