Triple
T38363508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Lange as Leigh Bowden |
E892360
|
entity |
| Predicate | runningTimeOfWork |
P1958
|
FINISHED |
| Object | approximately 128 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 128 minutes | Statement: [Jessica Lange as Leigh Bowden, runningTimeOfWork, approximately 128 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningTimeOfWork Context triple: [Jessica Lange as Leigh Bowden, runningTimeOfWork, approximately 128 minutes]
-
A.
runtimeOfWork
Indicates the duration of time required to complete a particular work or task.
-
B.
runtimeMinutes
chosen
Indicates the total duration of something, typically a media work or process, measured in minutes.
-
C.
workLength
Indicates the duration or length of time associated with a particular work or task.
-
D.
runsFor
Indicates that an entity performs a running activity on behalf of, or as a representative of, another entity (such as a team, organization, or cause).
-
E.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.