Triple
T27356699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Development Flight Instrumentation |
E685703
|
entity |
| Predicate | appliedToProgram |
P44502
|
FINISHED |
| Object | Space Shuttle Program |
—
|
NE NERFINISHED |
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: Space Shuttle Program | Statement: [Development Flight Instrumentation, appliedToProgram, Space Shuttle Program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToProgram Context triple: [Development Flight Instrumentation, appliedToProgram, Space Shuttle Program]
-
A.
appliesProgram
Indicates that an agent initiates or carries out a specific program, procedure, or course of action on or for a target entity.
-
B.
usedByProgram
chosen
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
C.
usedAsProgramFor
Indicates that one entity functions as the software or application used to operate, control, or provide services for another entity.
-
D.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
E.
affectsProgram
Indicates that one entity produces an influence or change on a program, altering its behavior, state, or outcome.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 11:51 a.m.