Triple
T35790919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GoFast UFO incident |
E1034688
|
entity |
| Predicate | objectStatus |
P184112
|
FINISHED |
| Object | unidentified |
—
|
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: unidentified | Statement: [GoFast UFO incident, objectStatus, unidentified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectStatus Context triple: [GoFast UFO incident, objectStatus, unidentified]
-
A.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
B.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
C.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
D.
opusStatus
Indicates the current state or condition of an artistic or literary work within its lifecycle (e.g., planned, in progress, completed, or published).
-
E.
structureStatus
Indicates the current condition or state of completion of a structure in relation to its intended design or function.
- 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_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.