Triple
T12008091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotspur |
E285833
|
entity |
| Predicate | firstPerformanceApproximate |
P102639
|
FINISHED |
| Object | 1597 |
—
|
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: 1597 | Statement: [Hotspur, firstPerformanceApproximate, 1597]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceApproximate Context triple: [Hotspur, firstPerformanceApproximate, 1597]
-
A.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
B.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
C.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
D.
firstPerformanceTheatre
Indicates the theatre where an entity (such as a play or performance) was first performed.
-
E.
firstPerformanceLanguage
Indicates the language in which a work was originally performed for the first time.
- F. None of above. chosen
Provenance (4 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d61a4c81909e6cb6500b61df94 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d9038e39f881908c58c19802ba2eb0 |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.