Triple
T25298492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tor-M2 |
E634281
|
entity |
| Predicate | radarFunction |
P158808
|
FINISHED |
| Object | target detection |
—
|
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: target detection | Statement: [Tor-M2, radarFunction, target detection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarFunction Context triple: [Tor-M2, radarFunction, target detection]
-
A.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another entity.
-
B.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
C.
radarConfiguration
Indicates a relationship where a radar system is associated with or defined by a specific configuration or setup of its operational parameters.
-
D.
radarModel
Indicates that one entity is a radar system and the other is the specific model or type designation of that radar.
-
E.
radarLocation
Indicates the geographic position where a radar system is installed or operating.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd5621481909935d022d9275194 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 1:22 p.m.