Triple
T38552963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohemian Montmartre |
E925160
|
entity |
| Predicate | attractedPerformer |
P191186
|
FINISHED |
| Object | Aristide Bruant |
—
|
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: Aristide Bruant | Statement: [Bohemian Montmartre, attractedPerformer, Aristide Bruant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractedPerformer Context triple: [Bohemian Montmartre, attractedPerformer, Aristide Bruant]
-
A.
attractedArtist
Indicates that one artist feels romantic or emotional attraction toward another artist.
-
B.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
C.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
D.
eligiblePerformers
Indicates that certain entities are qualified or permitted to perform in a specified event, role, or context.
-
E.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
- F. None of above. chosen
Provenance (4 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.