Triple
T16370722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-51A Waverider |
E397555
|
entity |
| Predicate | programStartApprox |
P48368
|
FINISHED |
| Object | early 2000s |
—
|
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 2000s | Statement: [X-51A Waverider, programStartApprox, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programStartApprox Context triple: [X-51A Waverider, programStartApprox, early 2000s]
-
A.
productionStartApproximate
Indicates that the start of production for something is known only approximately rather than as an exact date or time.
-
B.
programLaunch
Indicates the initiation or start of a software program or application.
-
C.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
D.
programOn
Indicates that a program is scheduled to be broadcast or presented on a particular channel, station, platform, or device.
-
E.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff414d808190beae2ff162e430f8 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.