Triple
T35790791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLIR1 |
E1034685
|
entity |
| Predicate | sensorPlatform |
P184189
|
FINISHED |
| Object | F/A-18 Super Hornet |
—
|
NE NERFINISHED |
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: F/A-18 Super Hornet | Statement: [FLIR1, sensorPlatform, F/A-18 Super Hornet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensorPlatform Context triple: [FLIR1, sensorPlatform, F/A-18 Super Hornet]
-
A.
edgePlatform
Indicates a platform or system that operates at the network edge, close to end devices or data sources, to provide localized processing or services.
-
B.
sensorProvider
Indicates that one entity serves as the source or supplier of sensor data or sensing capabilities for another entity.
-
C.
sensorClass
Indicates that one entity is classified as a type or category of sensor relative to another entity.
-
D.
sensorArchitecture
Indicates the structural design or configuration of a sensor system, including how its components are organized and interact to perform sensing functions.
-
E.
sensorsLocation
Indicates that a sensor is physically or logically situated at a specific location.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:06 p.m.