Triple
T18274135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Rocket Module URM-1 |
E437689
|
entity |
| Predicate | structuralDesign |
P131134
|
FINISHED |
| Object | modular |
—
|
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: modular | Statement: [Universal Rocket Module URM-1, structuralDesign, modular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralDesign Context triple: [Universal Rocket Module URM-1, structuralDesign, modular]
-
A.
structuralDesigner
Indicates that an entity is responsible for planning, analyzing, and designing the structural aspects of another entity (such as a building, bridge, or component).
-
B.
structuralAmbition
Indicates an entity’s intention or effort to change, shape, or influence an existing structure, system, or organizational framework.
-
C.
structuralSystemType
Indicates the type or classification of the structural system employed in or associated with an entity.
-
D.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
E.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50050d6688190b909a1c24e1dd3c9 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.