Triple
T2402165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Orbiter Mission |
E47792
|
entity |
| Predicate | MarsOrbitInsertionDate |
P37963
|
FINISHED |
| Object | 2014-09-24 |
—
|
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: 2014-09-24 | Statement: [Mars Orbiter Mission, MarsOrbitInsertionDate, 2014-09-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MarsOrbitInsertionDate Context triple: [Mars Orbiter Mission, MarsOrbitInsertionDate, 2014-09-24]
-
A.
enteredLunarOrbitDate
Indicates the date on which an object or spacecraft first entered into orbit around the Moon.
-
B.
firstSpacecraftArrivalDate
Indicates the calendar date on which the first spacecraft arrived at a specified destination or location.
-
C.
flybyDate
Indicates the date on which one object passes close to another in a flyby encounter.
-
D.
firstOrbitalLaunchAttemptDate
Indicates the calendar date on which an entity made its first attempt to launch a vehicle into orbit.
-
E.
enteredInterstellarSpaceDate
Indicates the date on which an object or entity crossed the boundary of its originating stellar system and entered interstellar space.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8f623908190875fdbc95c944f33 |
completed | March 7, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc664317c8190a6bb5a5065c21bde |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.