Triple
T10041812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBS 56 BILL |
E205312
|
entity |
| Predicate | operatorTask |
P91792
|
FINISHED |
| Object | keeps crosshairs on target |
—
|
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: keeps crosshairs on target | Statement: [RBS 56 BILL, operatorTask, keeps crosshairs on target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorTask Context triple: [RBS 56 BILL, operatorTask, keeps crosshairs on target]
-
A.
operationalTask
Indicates that an entity is engaged in, responsible for, or associated with a specific operational activity or task within a process or system.
-
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.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
D.
operatorPlanned
Indicates that an operator has scheduled or arranged a specific action, process, or operation to occur.
-
E.
operatorDuringOperation
Indicates that an operator is the one performing or responsible for an operation during its execution.
- F. None of above. chosen
Provenance (4 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:55 p.m.