Triple
T21135004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HL-20 Personnel Launch System |
E520793
|
entity |
| Predicate | entryMode |
P142987
|
FINISHED |
| Object | gliding approach and landing |
—
|
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: gliding approach and landing | Statement: [HL-20 Personnel Launch System, entryMode, gliding approach and landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryMode Context triple: [HL-20 Personnel Launch System, entryMode, gliding approach and landing]
-
A.
entryCondition
Indicates the prerequisite state, criteria, or circumstances that must be satisfied before entering or initiating a particular process, state, or context.
-
B.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
-
C.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
D.
entryDescription
Indicates that a text provides a descriptive summary or explanation of a particular entry or record.
-
E.
entrySelectionMethod
Indicates the method or criteria used to select or admit an entity into a particular group, system, or context.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723592fd48190ba5977a1b229d51e |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:56 p.m.