Triple
T20067595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariane |
E499648
|
entity |
| Predicate | workFirstPerformanceYear |
P99128
|
FINISHED |
| Object | 1664 |
—
|
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: 1664 | Statement: [Mariane, workFirstPerformanceYear, 1664]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFirstPerformanceYear Context triple: [Mariane, workFirstPerformanceYear, 1664]
-
A.
firstPerformanceOfWorkYear
chosen
Indicates that the referenced performance is the first time a particular work was performed in a given calendar year.
-
B.
firstEuropeanPerformanceYear
Indicates the year in which something (such as a work, event, or performance) was first performed in Europe.
-
C.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
D.
yearOfPerformance
Indicates the specific calendar year in which a performance, event, or action took place.
-
E.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66379f2cc81908f13a7b216878f12 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.