Triple
T7722440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | External Tank |
E175045
|
entity |
| Predicate | programUse |
P78781
|
FINISHED |
| Object | flown on every Space Shuttle launch |
—
|
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: flown on every Space Shuttle launch | Statement: [External Tank, programUse, flown on every Space Shuttle launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programUse Context triple: [External Tank, programUse, flown on every Space Shuttle launch]
-
A.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
-
B.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
C.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
D.
userProgram
Indicates that a user is associated with, uses, or is responsible for a particular program.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7074cd1f081908d5e8951660e7271 |
completed | March 27, 2026, 10:40 p.m. |
Created at: March 27, 2026, 4:05 p.m.