Triple
T29842508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ballerina |
E757838
|
entity |
| Predicate | workDesigner |
P28525
|
FINISHED |
| Object | Alexandre Benois |
—
|
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: Alexandre Benois | Statement: [The Ballerina, workDesigner, Alexandre Benois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workDesigner Context triple: [The Ballerina, workDesigner, Alexandre Benois]
-
A.
workDirector
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
B.
officeHeldByDesigner
Indicates that a particular office or official position is occupied or held by a given designer.
-
C.
designCollaboration
Indicates a collaborative relationship in which two or more entities jointly participate in the design process or co-create a design outcome.
-
D.
designLead
chosen
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designStarted
Indicates that the process of designing something has been initiated or begun.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760b3d6081909d0e3748483989a4 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:40 p.m.