Triple
T36878651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Wolf missile system (later refit) |
E911412
|
entity |
| Predicate | trackingSensor |
P189374
|
FINISHED |
| Object | tracking radar |
—
|
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: tracking radar | Statement: [Sea Wolf missile system (later refit), trackingSensor, tracking radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackingSensor Context triple: [Sea Wolf missile system (later refit), trackingSensor, tracking radar]
-
A.
tracksSensor
Indicates that one entity continuously monitors and records data from a specified sensor.
-
B.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
C.
trackingTechnology
Indicates that one entity uses or is associated with a technology designed to monitor, record, or follow the behavior, location, or interactions of another entity.
-
D.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
E.
trackSystem
Indicates a relationship where one entity monitors, records, or follows the status, behavior, or changes of another entity within a system.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:13 p.m.