Triple
T33212520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars orbiters |
E850196
|
entity |
| Predicate | firstSuccessfulExample |
P39493
|
FINISHED |
| Object | Mariner 9 |
E463796
|
NE 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: Mariner 9 | Statement: [Mars orbiters, firstSuccessfulExample, Mariner 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSuccessfulExample Context triple: [Mars orbiters, firstSuccessfulExample, Mariner 9]
-
A.
firstTest
Indicates that an entity is the initial or earliest test in a sequence or set of tests.
-
B.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
C.
earlySuccess
Indicates that an entity achieves notable success or positive outcomes at an unusually early stage relative to a typical timeline or peers.
-
D.
firstSuccessfulDemoMission
chosen
Indicates that the mission is the first demonstration mission that achieved its intended success.
-
E.
firstMajorSuccess
Indicates that an entity represents the earliest significant achievement or breakthrough in another entity’s career, activity, or development.
- F. None of above.
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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3551e9b63c81909bfaab3cf1487243 |
completed | June 19, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.