Triple
T8207623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Virtuous Sin |
E191725
|
entity |
| Predicate | hasRuntimeMinutes |
P1958
|
FINISHED |
| Object | 80 |
—
|
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: 80 | Statement: [The Virtuous Sin, hasRuntimeMinutes, 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuntimeMinutes Context triple: [The Virtuous Sin, hasRuntimeMinutes, 80]
-
A.
hasRunningTimeCategory
Indicates that an entity is associated with a specific category based on its running time or duration.
-
B.
runtimeMinutes
chosen
Indicates the total duration of something, typically a media work or process, measured in minutes.
-
C.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
D.
hasTimingCapability
Indicates that an entity possesses the ability to measure, control, or manage timing-related aspects of an operation or process.
-
E.
hasScreenTimeIn
Indicates that an entity appears on screen for a certain duration within a specified audiovisual work or segment.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb726d26ec8190957da68227f5ce61 |
completed | March 31, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.