Triple
T35135082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beauharnais family |
E1014547
|
entity |
| Predicate | producedRoyalConsortOf |
P84515
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Beauharnais family, producedRoyalConsortOf, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedRoyalConsortOf Context triple: [Beauharnais family, producedRoyalConsortOf, France]
-
A.
producedQueenConsort
chosen
Indicates that one entity gave rise to or is the origin of another entity who became a queen consort.
-
B.
typeOfMonarchConsort
Indicates the specific kind or category of monarch’s spouse (consort) that an entity is, such as queen consort, prince consort, or empress consort.
-
C.
monarchOfWhomConsort
Indicates that a person is the monarch (king/queen/ruler) of another person who is their consort (spouse).
-
D.
monarchConsortOf
Indicates that one person is the spouse of a reigning monarch, holding the role of consort to that monarch.
-
E.
monarchOfConsort
Indicates that one entity is the consort (spouse) of the reigning monarch of another entity (typically a state or territory).
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 3, 2026, 4:02 p.m.