Triple
T34626923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bourbon-Orléans |
E889162
|
entity |
| Predicate | providedMonarchOf |
P19578
|
FINISHED |
| Object | July Monarchy |
—
|
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: July Monarchy | Statement: [House of Bourbon-Orléans, providedMonarchOf, July Monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedMonarchOf Context triple: [House of Bourbon-Orléans, providedMonarchOf, July Monarchy]
-
A.
providedMonarchTo
chosen
Indicates that one entity supplied or installed a monarch (such as a king or queen) to rule over another entity.
-
B.
confirmedMonarch
Indicates that an entity has been formally recognized and validated as the legitimate monarch, typically through an official confirmation process.
-
C.
representedMonarch
Indicates that one entity formally acted on behalf of, or served as the official representative of, a monarch in some capacity or context.
-
D.
servedMonarch
Indicates that one entity held a position of service, allegiance, or duty under the authority of a particular monarch.
-
E.
monarchSubjectOf
Indicates that a monarch is the central topic or focus of a given statement, document, or informational resource.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 2:04 a.m.