Triple
T9387753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artisan 3D radar |
E225945
|
entity |
| Predicate | trackingCapability |
P18529
|
FINISHED |
| Object | air targets |
—
|
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: air targets | Statement: [Artisan 3D radar, trackingCapability, air targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackingCapability Context triple: [Artisan 3D radar, trackingCapability, air targets]
-
A.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
B.
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.
-
C.
trackingType
chosen
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
D.
trackingDetectorTechnology
Indicates that an entity uses or is associated with a specific technology for tracking detectors (devices that measure and reconstruct particle trajectories).
-
E.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d562a48190875d9fe3aae25a2b |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.