Triple
T9802364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jade |
E237869
|
entity |
| Predicate | hasScreenTimeImportance |
P38169
|
FINISHED |
| Object | major |
—
|
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: major | Statement: [Jade, hasScreenTimeImportance, major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenTimeImportance Context triple: [Jade, hasScreenTimeImportance, major]
-
A.
screenTimeImportance
chosen
Indicates how important or significant the amount of time spent using screens or digital devices is considered in a given context.
-
B.
hasScreenTimeIn
Indicates that an entity appears on screen for a certain duration within a specified audiovisual work or segment.
-
C.
screenTimeFocus
Indicates the amount or proportion of time an entity’s attention or activity is concentrated on a particular screen or digital display.
-
D.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
E.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62b41048190bcef70a7591830c6 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.