Triple
T3135977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exploration Upper Stage |
E65529
|
entity |
| Predicate | programStartApproximate |
P4785
|
FINISHED |
| Object | mid-2010s |
—
|
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: mid-2010s | Statement: [Exploration Upper Stage, programStartApproximate, mid-2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programStartApproximate Context triple: [Exploration Upper Stage, programStartApproximate, mid-2010s]
-
A.
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.
-
B.
programOn
Indicates that a program is scheduled to be broadcast or presented on a particular channel, station, platform, or device.
-
C.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
D.
activityStartApprox
chosen
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
E.
runtimeApprox
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5637de0819089393429c4017298 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.