Triple
T2962522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astrophysics Theory Program |
E80080
|
entity |
| Predicate | proposalMechanism |
P25604
|
FINISHED |
| Object | NASA ROSES solicitations |
—
|
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: NASA ROSES solicitations | Statement: [NASA Astrophysics Theory Program, proposalMechanism, NASA ROSES solicitations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalMechanism Context triple: [NASA Astrophysics Theory Program, proposalMechanism, NASA ROSES solicitations]
-
A.
negotiationMechanism
Indicates a process or method through which parties communicate and bargain to reach a mutually acceptable agreement.
-
B.
proposalProcess
chosen
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
resolutionMechanism
Indicates the method, process, or system used to resolve a conflict, issue, or discrepancy between entities.
-
E.
approvalMethod
Indicates the method or process by which approval is granted or obtained between entities.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9955e6488190bea170724d5fbfe8 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.