Triple
T38185326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michèle Bernstein |
E1005299
|
entity |
| Predicate | work described as |
P44666
|
FINISHED |
| Object | experimental |
—
|
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: experimental | Statement: [Michèle Bernstein, work described as, experimental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: work described as Context triple: [Michèle Bernstein, work described as, experimental]
-
A.
workDescribedIn
Indicates that a work (such as a publication or document) provides a description or account of the referenced entity.
-
B.
workDescribedAs
chosen
Indicates that one entity’s work, project, or output is characterized, labeled, or referred to by a particular description, title, or phrase.
-
C.
workDescribes
Indicates that one work (such as a document, artwork, or dataset) provides a description or explanatory account of another work.
-
D.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.