Triple
T33739481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother (Edina's mother) |
E864519
|
entity |
| Predicate | screenTimePattern |
P180909
|
FINISHED |
| Object | recurring 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: recurring character | Statement: [Mother (Edina's mother), screenTimePattern, recurring character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenTimePattern Context triple: [Mother (Edina's mother), screenTimePattern, recurring character]
-
A.
screenTime
Indicates the amount of time an entity spends viewing or interacting with a screen-based device.
-
B.
screenTimeRelation
Indicates a relationship between entities based on the amount, duration, or pattern of time spent using screens or digital devices.
-
C.
screenTimePhase
Indicates the specific stage or period within a broader screen-time process, session, or lifecycle that an entity is currently in.
-
D.
screenTimeFunction
Indicates a functional relationship that maps an entity (such as a user, device, or app) to the amount of time its screen is active or in use.
-
E.
screenTimeConcentratedIn
Indicates that the majority of an entity’s screen usage occurs within a specific time period or temporal window.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: May 1, 2026, 1:44 a.m.