Triple
T13488060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenable |
E318556
|
entity |
| Predicate | hasClosingSequence |
P20927
|
FINISHED |
| Object | reveal of final prize outcome |
—
|
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: reveal of final prize outcome | Statement: [Tenable, hasClosingSequence, reveal of final prize outcome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClosingSequence Context triple: [Tenable, hasClosingSequence, reveal of final prize outcome]
-
A.
hasClosingSectionCharacter
Indicates that something includes a specific character used to mark the end of a section.
-
B.
hasEnding
chosen
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
C.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
D.
isClosed
Indicates that an entity, process, or structure is in a finished, sealed, or non-open state, preventing further change or access.
-
E.
hasOpeningSequenceLocation
Indicates the specific location where the opening sequence of something (such as a film, show, or event) takes place.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.