Triple
T13546740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Launcher-1 |
E323530
|
entity |
| Predicate | usedDuringPhase |
P82971
|
FINISHED |
| Object | early Skylab program |
—
|
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: early Skylab program | Statement: [Mobile Launcher-1, usedDuringPhase, early Skylab program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDuringPhase Context triple: [Mobile Launcher-1, usedDuringPhase, early Skylab program]
-
A.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
typicalUsagePhase
Indicates the phase or stage in which something is most commonly or characteristically used.
-
C.
usedInStage
chosen
Indicates that something is utilized or applied during a particular stage or phase of a process or workflow.
-
D.
appliesToPhase
Indicates that a particular rule, condition, or action is relevant to and operates during a specific phase within a process or lifecycle.
-
E.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
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:45 p.m.