Triple
T26802499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | June Constitution |
E671137
|
entity |
| Predicate | monarchAtAdoption |
P62273
|
FINISHED |
| Object | Frederick VII of Denmark |
—
|
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: Frederick VII of Denmark | Statement: [June Constitution, monarchAtAdoption, Frederick VII of Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchAtAdoption Context triple: [June Constitution, monarchAtAdoption, Frederick VII of Denmark]
-
A.
monarchAfterCoronation
Indicates that one entity serves as the reigning monarch following the coronation event of another entity.
-
B.
monarchOnEstablishment
chosen
Indicates that a particular monarch holds or held the position of head of state for a given establishment (such as a country, state, or institution).
-
C.
monarchDesignate
Indicates that one entity is formally chosen or recognized as the future monarch of another entity or domain.
-
D.
monarchDuringBirth
Indicates that one entity was the reigning monarch at the time another entity was born.
-
E.
monarchAssociatedWith
Indicates a relationship where a monarch has a notable connection or affiliation with another entity, such as a person, place, institution, or event.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 4:24 a.m.