Triple
T36540473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The TV Movie |
E900705
|
entity |
| Predicate | attemptedRelaunchFor |
P41560
|
FINISHED |
| Object | international audience |
—
|
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: international audience | Statement: [The TV Movie, attemptedRelaunchFor, international audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedRelaunchFor Context triple: [The TV Movie, attemptedRelaunchFor, international audience]
-
A.
relaunch
chosen
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
B.
launchAttemptNumber
Indicates the ordinal count of attempts made to launch something, typically specifying which numbered try a particular launch event represents.
-
C.
renewalAttempt
Indicates an action where an existing agreement, subscription, or status is being tried to be renewed, typically after or near its expiration.
-
D.
launchAttemptCount
Indicates the number of times a launch has been attempted for the associated entity or event.
-
E.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.