Triple
T10896068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joey LaMotta |
E257312
|
entity |
| Predicate | screenTimeFunction |
P96278
|
FINISHED |
| Object | humanizes Jake LaMotta |
—
|
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: humanizes Jake LaMotta | Statement: [Joey LaMotta, screenTimeFunction, humanizes Jake LaMotta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenTimeFunction Context triple: [Joey LaMotta, screenTimeFunction, humanizes Jake LaMotta]
-
A.
screenTimeFocus
Indicates the amount or proportion of time an entity’s attention or activity is concentrated on a particular screen or digital display.
-
B.
hasScreenTimeIn
Indicates that an entity appears on screen for a certain duration within a specified audiovisual work or segment.
-
C.
screenTimeImportance
Indicates how important or significant the amount of time spent using screens or digital devices is considered in a given context.
-
D.
topScreenUsage
Indicates that an entity is the primary or most frequently used screen/interface within a given context or system.
-
E.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
- F. None of above. chosen
Provenance (4 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.