Triple
T24787248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASV radar |
E620151
|
entity |
| Predicate | rangeDomain |
P4679
|
FINISHED |
| Object | medium-range detection of surface 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: medium-range detection of surface targets | Statement: [ASV radar, rangeDomain, medium-range detection of surface targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeDomain Context triple: [ASV radar, rangeDomain, medium-range detection of surface targets]
-
A.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
B.
domainServed
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
C.
indicatesDomain
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
D.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
E.
range
chosen
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110071008190a430ca780b567fe4 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:46 a.m.