Triple
T5561337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REX |
E145771
|
entity |
| Predicate | missionPhaseUsed |
P53282
|
FINISHED |
| Object | Pluto flyby |
—
|
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: Pluto flyby | Statement: [REX, missionPhaseUsed, Pluto flyby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPhaseUsed Context triple: [REX, missionPhaseUsed, Pluto flyby]
-
A.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
B.
currentMissionPhase
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
C.
supportsMissionPhase
Indicates that one entity provides the necessary capabilities, resources, or conditions for another entity to function or be valid during a specific mission phase.
-
D.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
E.
usedByMission
chosen
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02019c6748190aeefb86f489f726a |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.