Triple
T13553237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshield and Interface Structure |
E323701
|
entity |
| Predicate | phaseUsed |
P110321
|
FINISHED |
| Object | 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: cruise to Mercury | Statement: [Sunshield and Interface Structure, phaseUsed, cruise to Mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseUsed Context triple: [Sunshield and Interface Structure, phaseUsed, cruise to Mercury]
-
A.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
B.
phaseType
Indicates the specific stage or phase category that an associated process, event, or lifecycle instance belongs to.
-
C.
phase
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
-
D.
phaseAppearance
Indicates the observable form or manifestation that an entity exhibits during a particular phase or stage of a process or cycle.
-
E.
phaseInStructure
Indicates that an entity occurs as a particular phase or stage within the structural organization or composition of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:46 p.m.