Triple
T3760022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan Bingham |
E82137
|
entity |
| Predicate | screenTimeFocus |
P50790
|
FINISHED |
| Object | central protagonist of Up in the Air |
—
|
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: central protagonist of Up in the Air | Statement: [Ryan Bingham, screenTimeFocus, central protagonist of Up in the Air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenTimeFocus Context triple: [Ryan Bingham, screenTimeFocus, central protagonist of Up in the Air]
-
A.
screenTimeImportance
Indicates how important or significant the amount of time spent using screens or digital devices is considered in a given context.
-
B.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
C.
focusPeriodStart
Indicates the point in time at which a specified focus period or interval begins.
-
D.
hasProgramFocus
Indicates that an entity (such as a program or initiative) is oriented around or primarily concerned with a particular thematic area, topic, or objective.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbc3d3f48190974cec104080949f |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:35 p.m.