Triple
T22756932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William VII, Landgrave of Hesse-Kassel |
E562870
|
entity |
| Predicate | heldFullGovernance |
P118045
|
FINISHED |
| Object | false |
—
|
LITERAL 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: false | Statement: [William VII, Landgrave of Hesse-Kassel, heldFullGovernance, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldFullGovernance Context triple: [William VII, Landgrave of Hesse-Kassel, heldFullGovernance, false]
-
A.
heldCouncil
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
B.
heldConfidenceVoteIn
Indicates that a confidence vote was conducted within a specified governing body, assembly, or context.
-
C.
hasGovernanceForm
chosen
Indicates that an entity is organized or administered according to a particular system or form of governance.
-
D.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
-
E.
holdsTo
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a798ae08190b9810bf241613198 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.