Triple
T29039096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unsolved Mysteries |
E737944
|
entity |
| Predicate | invitesAudienceTo |
P25673
|
FINISHED |
| Object | submit tips |
—
|
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: submit tips | Statement: [Unsolved Mysteries, invitesAudienceTo, submit tips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitesAudienceTo Context triple: [Unsolved Mysteries, invitesAudienceTo, submit tips]
-
A.
invitesParticipationOf
chosen
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
B.
invitationAuthority
Indicates that one entity has the authority or permission to invite another entity (or others) to participate in an event, group, or activity.
-
C.
invitesToLocation
Indicates that one entity extends an invitation to another entity to go to or be present at a specific location.
-
D.
isAudienceChoiceFor
Indicates that one entity represents a choice, option, or selection available to an audience in relation to another entity.
-
E.
invitesResponseOf
Indicates that one entity’s action, message, or state prompts, elicits, or calls for a response from another entity.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 10 a.m.