Triple
T1292388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourbonnais |
E27574
|
entity |
| Predicate | integratedIntoRoyalDomain |
P18474
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Bourbonnais, integratedIntoRoyalDomain, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoRoyalDomain Context triple: [Bourbonnais, integratedIntoRoyalDomain, 16th century]
-
A.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
B.
associatedWithMonarchy
chosen
Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
-
C.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
D.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
-
E.
kingdomAssociatedWith
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.