Triple
T9616210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honey, I Shrunk the Audience |
E232224
|
entity |
| Predicate | runTime |
P1958
|
FINISHED |
| Object | approximately 23 minutes |
—
|
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: approximately 23 minutes | Statement: [Honey, I Shrunk the Audience, runTime, approximately 23 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runTime Context triple: [Honey, I Shrunk the Audience, runTime, approximately 23 minutes]
-
A.
primaryRuntime
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
-
B.
originalRuntime
Indicates the initial or primary duration associated with something, typically before any edits, changes, or adjustments are made.
-
C.
runtimeMinutes
chosen
Indicates the total duration of something, typically a media work or process, measured in minutes.
-
D.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
E.
runsFrom
Indicates that one entity flees or escapes away 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aad71a0819084ea00c2409e9922 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.