Triple
T20687398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Heist |
E508454
|
entity |
| Predicate | independentlyReleased |
P22073
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Heist, independentlyReleased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: independentlyReleased Context triple: [The Heist, independentlyReleased, true]
-
A.
independentRelease
chosen
Indicates that a work was released independently, without the backing or involvement of a major external organization or label.
-
B.
independentlyDevelopedBy
Indicates that something was created or developed by an entity without collaboration, influence, or shared effort with others.
-
C.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
-
D.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
E.
notReleasedIn
Indicates that a particular item, such as a product or media work, has not been made available or launched in a specified location or market.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6beaddfe88190897b8963fa8b2245 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.