Triple
T4618338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 10 |
E100920
|
entity |
| Predicate | thirdMercuryFlybyDate |
P22034
|
FINISHED |
| Object | 1975-03-16 |
—
|
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: 1975-03-16 | Statement: [Mariner 10, thirdMercuryFlybyDate, 1975-03-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMercuryFlybyDate Context triple: [Mariner 10, thirdMercuryFlybyDate, 1975-03-16]
-
A.
flybyDate
chosen
Indicates the date on which one object passes close to another in a flyby encounter.
-
B.
NeptuneFlybyDate
Indicates the date on which a spacecraft performs or performed a flyby of Neptune.
-
C.
firstSuccessfulFlybyBy
Indicates that the subject is the first spacecraft or mission to successfully perform a flyby of the object specified by the predicate’s value.
-
D.
firstFlybyYear
Indicates the calendar year in which an object or mission first performed a flyby of a specified target.
-
E.
plannedMercuryOrbitInsertion
Indicates that an entity has scheduled or intends to perform the maneuver required to place a spacecraft into orbit around Mercury.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.