Triple
T23472808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry IV (play) |
E570172
|
entity |
| Predicate | periodOfFirstPerformance |
P94859
|
FINISHED |
| Object | early 1920s |
—
|
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: early 1920s | Statement: [Henry IV (play), periodOfFirstPerformance, early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfFirstPerformance Context triple: [Henry IV (play), periodOfFirstPerformance, early 1920s]
-
A.
dateOfFirstPerformance
Indicates the date on which a work, such as a play or musical composition, was first publicly performed.
-
B.
firstPerformedDuring
chosen
Indicates that an action, event, or performance occurred for the first time within a specified time period or during a particular event.
-
C.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
D.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
E.
placeOfFirstPerformance
Indicates the location where a work (such as a play, musical piece, or performance) was first publicly performed.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70244208190bbd8f58ac16d4399 |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:57 p.m.