Triple
T471249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/TPY-2 |
E8560
|
entity |
| Predicate | operatorInterface |
P11686
|
FINISHED |
| Object | remote control shelter |
—
|
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: remote control shelter | Statement: [AN/TPY-2, operatorInterface, remote control shelter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorInterface Context triple: [AN/TPY-2, operatorInterface, remote control shelter]
-
A.
usesInterface
chosen
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
B.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
D.
operator
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
E.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff0ca408190958405aec2ec6f53 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.