Triple
T25750358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stardust |
E648454
|
entity |
| Predicate | extendedMissionEncounterDate |
P32455
|
FINISHED |
| Object | 2011-02-15 |
—
|
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: 2011-02-15 | Statement: [Stardust, extendedMissionEncounterDate, 2011-02-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedMissionEncounterDate Context triple: [Stardust, extendedMissionEncounterDate, 2011-02-15]
-
A.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
B.
extensionEffectiveDate
chosen
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
C.
leaseExtendedUntil
Indicates that an existing lease agreement has been prolonged so that its validity now continues up to a specified end date.
-
D.
extendedOversightTo
Indicates that one entity has broadened or expanded its supervisory or regulatory authority to include another entity or domain.
-
E.
extendedIndefinitelyOn
Indicates that something was prolonged or continued without a specified end point in relation to something else.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 4:34 a.m.