Triple
T13353043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 2 |
E318115
|
entity |
| Predicate | notableReuse |
P91997
|
FINISHED |
| Object | capsule later reused for USAF MOL test as OPS 0855 |
—
|
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: capsule later reused for USAF MOL test as OPS 0855 | Statement: [Gemini 2, notableReuse, capsule later reused for USAF MOL test as OPS 0855]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableReuse Context triple: [Gemini 2, notableReuse, capsule later reused for USAF MOL test as OPS 0855]
-
A.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
B.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
C.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
D.
notableReaccession
Indicates a significant or noteworthy instance of something being reacquired, reaccepted, or readmitted after having previously left or been removed.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8d520881908aa23c7102b72b72 |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:32 p.m.