Triple
T21134994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HL-20 Personnel Launch System |
E520793
|
entity |
| Predicate | fullScaleMockup |
P116650
|
FINISHED |
| Object | built for human-factors testing |
—
|
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: built for human-factors testing | Statement: [HL-20 Personnel Launch System, fullScaleMockup, built for human-factors testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullScaleMockup Context triple: [HL-20 Personnel Launch System, fullScaleMockup, built for human-factors testing]
-
A.
scaleModelOf
chosen
Indicates that one entity is a scaled representation (larger or smaller but proportionally accurate) of another entity.
-
B.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
-
C.
mockedBy
Indicates that one entity ridicules, teases, or makes fun of another entity.
-
D.
exhibitionScale
Indicates the relative size, scope, or extent of an exhibition in which an entity is presented or involved.
-
E.
EiffelTowerReplicaScale
Indicates that one structure is a replica of the Eiffel Tower at a specified scale relative to the original.
- 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_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. |
Created at: April 16, 2026, 2:56 p.m.