Triple
T12254752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ELA-4 launch complex |
E292069
|
entity |
| Predicate | designedForReusabilitySupport |
P21235
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [ELA-4 launch complex, designedForReusabilitySupport, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForReusabilitySupport Context triple: [ELA-4 launch complex, designedForReusabilitySupport, no]
-
A.
designedForReusability
chosen
Indicates that something has been intentionally created or configured so it can be used multiple times without needing to be discarded or fundamentally rebuilt.
-
B.
reusability
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
C.
reusabilityImpact
Indicates how the ability to reuse something (such as a component, resource, or design) affects outcomes, performance, or other relevant factors in a given context.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.