Triple
T31350178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodolphe |
E799565
|
entity |
| Predicate | fictionalWorkFeaturingName |
P169860
|
FINISHED |
| Object | Madame Bovary |
—
|
NE NERFINISHED |
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: Madame Bovary | Statement: [Rodolphe, fictionalWorkFeaturingName, Madame Bovary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalWorkFeaturingName Context triple: [Rodolphe, fictionalWorkFeaturingName, Madame Bovary]
-
A.
fictionalCharacterPortrayedFromWorkBy
Indicates that a fictional character is depicted or portrayed in a work that was created by a specific author or creator.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
персонажПроизведения
chosen
Indicates a relationship where a person or entity is a character appearing in a particular literary or artistic work.
-
D.
composerOfWorkFeaturingCharacter
Indicates that one entity is the composer of a musical or dramatic work in which the other entity appears as a character.
-
E.
publisherOfWorksFeaturingCharacter
Indicates that one entity is the publisher responsible for releasing works in which a given character appears.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 29, 2026, 9:17 p.m.