Triple
T23442164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IIIA |
E565431
|
entity |
| Predicate | usedAsTestbedFor |
P23056
|
FINISHED |
| Object | military space technologies |
—
|
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: military space technologies | Statement: [Titan IIIA, usedAsTestbedFor, military space technologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTestbedFor Context triple: [Titan IIIA, usedAsTestbedFor, military space technologies]
-
A.
isUsedToTest
chosen
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
B.
testedUnder
Indicates that one entity is examined, evaluated, or experimented on while being subject to the conditions, environment, or parameters specified by another entity.
-
C.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
D.
alsoUsedBy
Indicates that something is additionally utilized or employed by another entity, beyond any primary or previously mentioned user.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64654e88190b530958b27b32412 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:51 p.m.