Triple
T33515763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Danube |
E858360
|
entity |
| Predicate | firstTested |
—
|
GENERATED |
| Object | early 1950s |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTested Context triple: [Blue Danube, firstTested, early 1950s]
-
A.
firstTestedBy
Indicates that an item, concept, or process was initially tested or tried out by a particular agent or entity.
-
B.
firstTest
Indicates that an entity is the initial or earliest test in a sequence or set of tests.
-
C.
firstTestYear
chosen
Indicates the year in which an entity’s first test or testing activity took place.
-
D.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
E.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
- F. None of above.
Provenance (1 batch)
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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.