Triple
T33790155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of 19 George II, c.39 |
E865909
|
entity |
| Predicate | monarchInRegnalTitle |
P98286
|
FINISHED |
| Object | George II |
—
|
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: George II | Statement: [Act of 19 George II, c.39, monarchInRegnalTitle, George II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchInRegnalTitle Context triple: [Act of 19 George II, c.39, monarchInRegnalTitle, George II]
-
A.
monarchTitleIn
Indicates that a particular monarch holds or held a specific royal title within a given political or territorial entity.
-
B.
styleOfMonarchTitle
Indicates the specific formal style or wording used in the official title of a monarch.
-
C.
monarchTitleUsedBy
chosen
Indicates that a particular monarchic title is or has been borne by a specific monarch or holder of the crown.
-
D.
monarchicTitleHolderOf
Indicates that one entity holds a monarchic title associated with another entity (such as a realm, position, or office).
-
E.
monarchTitleAtCoronation
Indicates the specific royal title a monarch held at the moment of their coronation.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:45 a.m.