Triple
T6044125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trick |
E134622
|
entity |
| Predicate | screenTimeScope |
P62983
|
FINISHED |
| Object | single-episode character |
—
|
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: single-episode character | Statement: [Trick, screenTimeScope, single-episode character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenTimeScope Context triple: [Trick, screenTimeScope, single-episode character]
-
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
chosen
Indicates that an entity appears on screen for a certain duration within a specified audiovisual work or segment.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e2b1148190908c4dc43abee266 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.