Triple
T30975555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry IV of France |
E789220
|
entity |
| Predicate | firstBourbonKingOf |
P3535
|
FINISHED |
| Object | France |
E861
|
NE 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: France | Statement: [Henry IV of France, firstBourbonKingOf, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBourbonKingOf Context triple: [Henry IV of France, firstBourbonKingOf, France]
-
A.
primaryMonarchBourbonSide
Indicates that the primary monarch in question belongs to, or rules from, the Bourbon royal lineage or faction.
-
B.
firstMonarch
chosen
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
C.
initiatedUnderMonarch
Indicates that an action, process, or event was begun during the reign or authority of a specific monarch.
-
D.
secondMonarch
Indicates that one entity is the second monarch (in chronological order of reign) in relation to another specified realm, dynasty, or succession context.
-
E.
royalistLeader
Indicates that one entity is the leader of a royalist faction, movement, or cause in relation to another entity.
- F. None of above.
Provenance (4 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fba4d3e48190a2c2729b968d8e9a |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: April 29, 2026, 8:55 p.m.