Triple
T18710359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darrell |
E457489
|
entity |
| Predicate | hasScreenTimeRole |
P101227
|
FINISHED |
| Object | lead role |
—
|
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: lead role | Statement: [Darrell, hasScreenTimeRole, lead role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenTimeRole Context triple: [Darrell, hasScreenTimeRole, lead role]
-
A.
screenTimeRole
chosen
Indicates the role or capacity in which an entity appears on screen, such as main, supporting, cameo, or other participation type.
-
B.
hasScreenTimeIn
Indicates that an entity appears on screen for a certain duration within a specified audiovisual work or segment.
-
C.
hasScreenTimeType
Indicates the type or category of screen time associated with an entity (e.g., usage mode, content type, or context of screen use).
-
D.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
E.
screenTime
Indicates the amount of time an entity spends viewing or interacting with a screen-based device.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671b34508190b6180f7d6ad50a58 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.