Triple
T30847050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Noces |
E785665
|
entity |
| Predicate | originalDesignsBy |
P80817
|
FINISHED |
| Object | Natalia Goncharova |
—
|
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: Natalia Goncharova | Statement: [Les Noces, originalDesignsBy, Natalia Goncharova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDesignsBy Context triple: [Les Noces, originalDesignsBy, Natalia Goncharova]
-
A.
designsBy
chosen
Indicates that one entity is the creator or designer responsible for the conception or design of another entity.
-
B.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
C.
currentDesign
Indicates that an entity is the presently active or most up-to-date design associated with another entity or context.
-
D.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
E.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: April 29, 2026, 8:46 p.m.