Triple
T38479436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Module C-020 |
E915629
|
entity |
| Predicate | recoveryAgency |
P43400
|
FINISHED |
| Object | U.S. Navy |
—
|
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: U.S. Navy | Statement: [Command Module C-020, recoveryAgency, U.S. Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveryAgency Context triple: [Command Module C-020, recoveryAgency, U.S. Navy]
-
A.
recoveryBy
Indicates that one entity regains or restores something (such as health, function, or a resource) through the action, intervention, or influence of another entity.
-
B.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
C.
relevantAgency
Indicates that an agency has authority, responsibility, or significant involvement in relation to a particular matter, entity, or action.
-
D.
splashdownRecoveryAgency
chosen
Indicates the organization responsible for recovering a spacecraft and its crew or cargo after splashdown.
-
E.
recoveryMethod
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.