Triple
T9413703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDPE-3A |
E226762
|
entity |
| Predicate | payloadRole |
P89019
|
FINISHED |
| Object | secondary payload adapter |
—
|
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: secondary payload adapter | Statement: [LDPE-3A, payloadRole, secondary payload adapter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadRole Context triple: [LDPE-3A, payloadRole, secondary payload adapter]
-
A.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
encodingRole
Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
proofRole
Indicates the specific function or responsibility an entity has within the structure or presentation of a proof.
-
E.
payloadSpecialist
Indicates that an entity serves in the role of a payload specialist, responsible for managing or operating specific payloads or experiments in a mission or operation.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c680e48190be82e3829e8711f0 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:47 p.m.