Triple
T36409719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Video Home System |
E896842
|
entity |
| Predicate | typicalRecordingTimeSP |
P203324
|
FINISHED |
| Object | 120 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: 120 minutes | Statement: [Video Home System, typicalRecordingTimeSP, 120 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRecordingTimeSP Context triple: [Video Home System, typicalRecordingTimeSP, 120 minutes]
-
A.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
B.
typicalDurationMinutes
chosen
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
C.
recordDuration
Indicates the length of time for which something is recorded or captured.
-
D.
typicalMasterDuration
Indicates the usual or standard length of time for which a master (e.g., a primary or controlling entity) remains in effect or holds its role.
-
E.
segmentDurationTypical
Indicates that the duration of a segment is considered typical or representative for that kind of 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.