Triple
T35429688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 248/6 |
E1024019
|
entity |
| Predicate | approximateFirstPerformanceDate |
P199844
|
FINISHED |
| Object | 1735 |
—
|
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: 1735 | Statement: [248/6, approximateFirstPerformanceDate, 1735]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateFirstPerformanceDate Context triple: [248/6, approximateFirstPerformanceDate, 1735]
-
A.
initialReleaseApprox
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
B.
firstBetaReleaseDate
Indicates the calendar date on which the first beta version of something was released.
-
C.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
D.
firstShortReleaseDate
Indicates the earliest (first) date on which a short version or short-format release of something became publicly available.
-
E.
launchDatePrecision
Indicates the level of exactness (such as year, month, or day) with which the launch date of something is specified.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
| PDg | Predicate description generation | batch_69ff5b224b8c8190bd0955876098ecc8 |
completed | May 9, 2026, 4:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.