Triple
T36957954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armadillo Aerospace |
E914235
|
entity |
| Predicate | developed |
P73
|
FINISHED |
| Object |
Stig-A rocket vehicle
Stig-A rocket vehicle is a suborbital reusable rocket developed by Armadillo Aerospace for experimental and commercial spaceflight missions.
|
E2207622
|
NE 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: Stig-A rocket vehicle | Statement: [Armadillo Aerospace, developed, Stig-A rocket vehicle]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Stig-A rocket vehicle Triple: [Armadillo Aerospace, developed, Stig-A rocket vehicle]
Generated description
Stig-A rocket vehicle is a suborbital reusable rocket developed by Armadillo Aerospace for experimental and commercial spaceflight missions.
Provenance (5 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9ff023d7481908e9f2516afa94bbd |
completed | May 5, 2026, 2:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c3c186481908121c17a9f397680 |
completed | June 26, 2026, 7:37 a.m. |
| NEDg | Description generation | batch_6a3e30367af481909b98f9b9741fafdb |
completed | June 26, 2026, 7:54 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a3e4c92061c8190b9fd29d0d389d9a3 |
completed | June 26, 2026, 9:55 a.m. |
Created at: May 3, 2026, 4:13 p.m.