Triple
T35842914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Fravor |
E1036133
|
entity |
| Predicate | allegedSensorDataAssociatedWithEvent |
P59649
|
FINISHED |
| Object | FLIR video from F/A-18 aircraft |
—
|
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: FLIR video from F/A-18 aircraft | Statement: [David Fravor, allegedSensorDataAssociatedWithEvent, FLIR video from F/A-18 aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedSensorDataAssociatedWithEvent Context triple: [David Fravor, allegedSensorDataAssociatedWithEvent, FLIR video from F/A-18 aircraft]
-
A.
isLinkedToEvent
chosen
Indicates that an entity has an association or connection with a specific event.
-
B.
allegedStartEvent
Indicates that an entity is claimed or reported (but not confirmed) to be the starting point or initiation of a particular event or process.
-
C.
dataCaptured
Indicates that some form of data has been recorded or collected from a source or process.
-
D.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
E.
trackingSensor
Indicates that a sensor is monitoring, recording, or following the state, position, or behavior of a target entity over time.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:06 p.m.