Triple
T16949781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Vehicle 4 |
E411151
|
entity |
| Predicate | testedSubsystem |
P109047
|
FINISHED |
| Object | guidance and control systems |
—
|
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: guidance and control systems | Statement: [Test Vehicle 4, testedSubsystem, guidance and control systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedSubsystem Context triple: [Test Vehicle 4, testedSubsystem, guidance and control systems]
-
A.
testedProcess
Indicates that an entity has performed a test or evaluation on a specific process.
-
B.
testedSystems
chosen
Indicates that an entity has performed tests on one or more systems to evaluate their behavior, performance, or correctness.
-
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.
replacedSubsystem
Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
-
E.
testedWith
Indicates that one entity has been examined, evaluated, or verified using another entity as the test method, tool, or counterpart.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb570b08190ae3385b0cad32668 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.