Triple
T26637782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Britain during the War of the Second Coalition |
E668685
|
entity |
| Predicate | hasRulerHouse |
P8992
|
FINISHED |
| Object | House of Hanover |
—
|
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: House of Hanover | Statement: [Great Britain during the War of the Second Coalition, hasRulerHouse, House of Hanover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerHouse Context triple: [Great Britain during the War of the Second Coalition, hasRulerHouse, House of Hanover]
-
A.
hasTypeOfRuler
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs another entity.
-
B.
hasRulerProclaimed
Indicates that a ruler has formally announced, declared, or publicly proclaimed something.
-
C.
hasRoyalHouse
chosen
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
D.
hasSignificantRuler
Indicates that an entity has or had a ruler whose leadership is considered historically or contextually important.
-
E.
hasRulingFamilyResidence
Indicates that a location serves as the primary home or official residence of a ruling family.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:28 a.m.