Triple
T13553386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTM |
E323704
|
entity |
| Predicate | cruisePhase |
P53563
|
FINISHED |
| Object | interplanetary cruise to Mercury |
—
|
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: interplanetary cruise to Mercury | Statement: [MTM, cruisePhase, interplanetary cruise to Mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cruisePhase Context triple: [MTM, cruisePhase, interplanetary cruise to Mercury]
-
A.
cruiseSpeed
Indicates the typical or optimal speed at which an entity is intended to travel under normal operating conditions.
-
B.
flightPhase
chosen
Indicates the specific stage or phase of an aircraft’s operation within a flight (e.g., taxi, takeoff, climb, cruise, descent, landing).
-
C.
cruiseCapability
Indicates the ability of an entity to travel or operate in a steady, sustained cruising mode under its own power.
-
D.
cruiseStageMass
Indicates the mass associated specifically with the cruise stage portion of a spacecraft during its mission.
-
E.
hasCruiseTraffic
Indicates that there is cruise ship traffic occurring at or involving a particular location or route.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:46 p.m.