Triple
T4618335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 10 |
E100920
|
entity |
| Predicate | numberOfMercuryFlybys |
P56987
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Mariner 10, numberOfMercuryFlybys, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMercuryFlybys Context triple: [Mariner 10, numberOfMercuryFlybys, 3]
-
A.
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.
-
B.
plannedMercuryOrbitInsertion
Indicates that an entity has scheduled or intends to perform the maneuver required to place a spacecraft into orbit around Mercury.
-
C.
firstFlybyBy
Indicates that one entity was the spacecraft, probe, or mission that performed the first flyby of another entity (such as a celestial body or target).
-
D.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
E.
orbitsCompletedAroundMars
Indicates the number of full orbital revolutions an object has completed around Mars.
- F. None of above. chosen
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_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. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.