Triple
T37685016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps aviation combat element command and control system |
E938340
|
entity |
| Predicate | sensorTypes |
P184110
|
FINISHED |
| Object | radar sensors |
—
|
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: radar sensors | Statement: [Marine Corps aviation combat element command and control system, sensorTypes, radar sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensorTypes Context triple: [Marine Corps aviation combat element command and control system, sensorTypes, radar sensors]
-
A.
sensorTypesInvolved
chosen
Indicates the types of sensors that participate in or are utilized within a given event, process, or system.
-
B.
sensorTypesPermitted
Indicates that certain types or categories of sensors are allowed or authorized for use in a given context or configuration.
-
C.
sensorClass
Indicates that one entity is classified as a type or category of sensor relative to another entity.
-
D.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
E.
sensorArchitecture
Indicates the structural design or configuration of a sensor system, including how its components are organized and interact to perform sensing functions.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.