Triple
T29634689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrambam |
E755678
|
entity |
| Predicate | hasBoxOfficeStatus |
P11911
|
FINISHED |
| Object | commercial success |
—
|
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: commercial success | Statement: [Arrambam, hasBoxOfficeStatus, commercial success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoxOfficeStatus Context triple: [Arrambam, hasBoxOfficeStatus, commercial success]
-
A.
hasBoxOffice
Indicates that an entity (typically a film or performance) has a specific box office revenue amount or record associated with it.
-
B.
hasBoxOfficeType
Indicates the classification of a work’s box office performance or revenue category (e.g., type or scale of its box office results).
-
C.
boxOfficeStatus
chosen
Indicates the commercial performance or financial success status of a film or media release at the box office.
-
D.
boxOfficeReportingUnit
Indicates the unit or scale (e.g., currency, region, or measurement basis) in which box office revenue figures are reported.
-
E.
rottenTomatoesStatus
Indicates the critical or audience evaluation status of a work as represented on Rotten Tomatoes (e.g., fresh, rotten, or certified).
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 6:43 p.m.