Triple
T4864443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Interoperability Test Command |
E108733
|
entity |
| Predicate | performsTestOn |
P17991
|
FINISHED |
| Object | command 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: command and control systems | Statement: [Joint Interoperability Test Command, performsTestOn, command and control systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsTestOn Context triple: [Joint Interoperability Test Command, performsTestOn, command and control systems]
-
A.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
B.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
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.
appliedTest
chosen
Indicates that a test has been administered or carried out on a particular subject or object.
-
E.
testingMethod
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7718e48190af4c0d1abfa87795 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.