Triple
T13349972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 Shag Harbour incident |
E318043
|
entity |
| Predicate | statusInUfology |
P68225
|
FINISHED |
| Object | classic UFO case |
—
|
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: classic UFO case | Statement: [1967 Shag Harbour incident, statusInUfology, classic UFO case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInUfology Context triple: [1967 Shag Harbour incident, statusInUfology, classic UFO case]
-
A.
allegedPhenomenon
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
-
B.
sightingState
chosen
Indicates the current status or condition of a reported sighting within its tracking or verification process.
-
C.
loreStatus
Indicates the canonical or contextual standing of something within a fictional or narrative universe (such as whether it is official, speculative, or non-canonical lore).
-
D.
isExtraterrestrial
Indicates that an entity originates from or belongs to a location beyond Earth.
-
E.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8c2f1c819094f0970f35f18afa |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.