Triple
T35790782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLIR1 |
E1034685
|
entity |
| Predicate | publicizedAs |
P8467
|
FINISHED |
| Object | evidence of unidentified aerial phenomenon |
—
|
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: evidence of unidentified aerial phenomenon | Statement: [FLIR1, publicizedAs, evidence of unidentified aerial phenomenon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicizedAs Context triple: [FLIR1, publicizedAs, evidence of unidentified aerial phenomenon]
-
A.
publiclySharedAs
Indicates that something has been made accessible to the general public in a shared or published form.
-
B.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
C.
publiclyAnnouncedBy
Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
-
D.
becamePublic
Indicates that an entity transitioned from private or restricted status to being publicly accessible or publicly traded.
-
E.
announcedAs
chosen
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:06 p.m.