Triple
T1042020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falling Skies |
E22488
|
entity |
| Predicate | premise |
P23849
|
FINISHED |
| Object | survivors resist alien invasion of Earth |
—
|
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: survivors resist alien invasion of Earth | Statement: [Falling Skies, premise, survivors resist alien invasion of Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premise Context triple: [Falling Skies, premise, survivors resist alien invasion of Earth]
-
A.
precondition
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
B.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
C.
preempts
Indicates that one action, decision, or rule takes priority over and prevents the application or effect of another.
-
D.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
E.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8444f708190815732408aa0463e |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.