Triple
T33064007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dauphin (Charles VII) in Saint Joan |
E846046
|
entity |
| Predicate | crownedThrough |
P24696
|
FINISHED |
| Object | Joan of Arc’s intervention |
—
|
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: Joan of Arc’s intervention | Statement: [The Dauphin (Charles VII) in Saint Joan, crownedThrough, Joan of Arc’s intervention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crownedThrough Context triple: [The Dauphin (Charles VII) in Saint Joan, crownedThrough, Joan of Arc’s intervention]
-
A.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
-
B.
crownedBy
chosen
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
-
C.
crownedAt
Indicates the place or event where an entity formally received a crown or was officially installed as a monarch or titleholder.
-
D.
crownPresent
Indicates that a crown is currently present on or with the relevant entity.
-
E.
crownDepicted
Indicates that one entity visually represents or shows a crown associated with another entity.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.