Triple
T249403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Space Shuttle program |
E5108
|
entity |
| Predicate | nonReusableComponent |
P5431
|
FINISHED |
| Object | external tank |
—
|
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: external tank | Statement: [NASA Space Shuttle program, nonReusableComponent, external tank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonReusableComponent Context triple: [NASA Space Shuttle program, nonReusableComponent, external tank]
-
A.
reusability
chosen
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
B.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
C.
notTypicallyUsedFor
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
D.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
E.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d3728f0819086214ccc2db2305a |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.