Triple
T28955968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of the French |
E731163
|
entity |
| Predicate | triggerEventOfEstablishment |
P36079
|
FINISHED |
| Object | overthrow of Charles X |
—
|
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: overthrow of Charles X | Statement: [Kingdom of the French, triggerEventOfEstablishment, overthrow of Charles X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerEventOfEstablishment Context triple: [Kingdom of the French, triggerEventOfEstablishment, overthrow of Charles X]
-
A.
establishedOnEvent
chosen
Indicates that something (such as a relationship, status, or entity) was created, initiated, or formally established as a direct result of a specific event.
-
B.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
establishedForEvent
Indicates that something (such as an organization, structure, or arrangement) was created or set up specifically for a particular event.
-
D.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
E.
triggerEventLocation
Indicates the location where a triggering event occurs or is initiated.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 8:47 a.m.