Triple
T20041836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourbon coalition |
E497438
|
entity |
| Predicate | allianceSystem |
P9451
|
FINISHED |
| Object | Bourbon family compact system |
—
|
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: Bourbon family compact system | Statement: [Bourbon coalition, allianceSystem, Bourbon family compact system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceSystem Context triple: [Bourbon coalition, allianceSystem, Bourbon family compact system]
-
A.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
C.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
D.
alliancesAround
Indicates that alliances are formed or exist in the vicinity or context of a specified entity or focal point.
-
E.
allianceType
chosen
Indicates the specific kind or category of alliance relationship that exists between entities.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eb9a6081909d06dc1d457b4d5a |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.