Triple
T27235109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flight 714 to Sydney |
E682250
|
entity |
| Predicate | hasRescueBy |
P91510
|
FINISHED |
| Object | extraterrestrials |
—
|
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: extraterrestrials | Statement: [Flight 714 to Sydney, hasRescueBy, extraterrestrials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRescueBy Context triple: [Flight 714 to Sydney, hasRescueBy, extraterrestrials]
-
A.
attemptedRescueBy
Indicates an action where one entity made an effort to save or free another entity from danger, harm, or a problematic situation.
-
B.
rescueBy
chosen
Indicates that one entity is saved or freed from danger, harm, or a problematic situation by another entity.
-
C.
seeksToRescue
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
D.
rescuesWith
Indicates that one entity saves or frees another entity from danger, harm, or captivity using a particular means, tool, or method.
-
E.
rescuedByProxy
Indicates that an entity is saved or freed from danger or harm through the actions or intervention of an intermediary acting on behalf of another.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 27, 2026, 9:47 a.m.