Triple
T4556439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live and Learn |
E120490
|
entity |
| Predicate | featuresFictionalEvent |
P6628
|
FINISHED |
| Object | alien invasion |
—
|
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: alien invasion | Statement: [Live and Learn, featuresFictionalEvent, alien invasion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFictionalEvent Context triple: [Live and Learn, featuresFictionalEvent, alien invasion]
-
A.
featuresEvent
chosen
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
B.
featuresFictionalSport
Indicates that a work includes or showcases a fictional sport as part of its content or setting.
-
C.
featuresReturnOf
Indicates that something (such as a work, event, or product) includes or highlights the comeback or reappearance of a person, character, element, or feature.
-
D.
featuresFictionalVirus
Indicates that a work includes or depicts a fictional virus as part of its content or storyline.
-
E.
featuresFictionalMusical
Indicates that a work includes or prominently involves a fictional musical as part of its content or storyline.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5814f56c8190a65f61f6148b7e5a |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.