Triple
T35791135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Colorado UFO Project |
E1034693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UFO research project |
C63358
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: UFO research project Context triple: [University of Colorado UFO Project, instanceOf, UFO research project]
-
A.
UFO investigation report
A UFO investigation report is a structured document that records the circumstances, evidence, analyses, and conclusions related to a reported unidentified flying object sighting or encounter.
-
B.
UFO investigation program
chosen
A UFO investigation program is an organized initiative, often run by governments or research groups, that systematically collects, analyzes, and evaluates reports of unidentified flying objects to determine their origin and assess potential security or scientific implications.
-
C.
UFO investigation file
A UFO investigation file is a structured record compiling reports, evidence, analyses, and conclusions related to a specific unidentified flying object sighting or incident.
-
D.
unidentified aerial phenomenon
An unidentified aerial phenomenon is any observed object or light in the sky whose nature, origin, or behavior cannot be readily explained by known aircraft, natural phenomena, or human-made technology.
-
E.
SETI experiment
A SETI experiment is a scientific investigation designed to detect potential signals or other evidence of intelligent extraterrestrial life using astronomical observations and signal analysis techniques.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:06 p.m.