Triple
T33049621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Atossa |
E845687
|
entity |
| Predicate | timeOfFirstKnownPerformanceOfWork |
P21118
|
FINISHED |
| Object | 472 BC |
—
|
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: 472 BC | Statement: [Queen Atossa, timeOfFirstKnownPerformanceOfWork, 472 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFirstKnownPerformanceOfWork Context triple: [Queen Atossa, timeOfFirstKnownPerformanceOfWork, 472 BC]
-
A.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
B.
dateOfFirstPerformance
chosen
Indicates the date on which a work, such as a play or musical composition, was first publicly performed.
-
C.
firstPerformanceOfWorkYear
Indicates that the referenced performance is the first time a particular work was performed in a given calendar year.
-
D.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
-
E.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:24 a.m.