Triple
T37163431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWDC live streams |
E920734
|
entity |
| Predicate | timeAlignment |
P53617
|
FINISHED |
| Object | synchronized with in‑person WWDC schedule |
—
|
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: synchronized with in‑person WWDC schedule | Statement: [WWDC live streams, timeAlignment, synchronized with in‑person WWDC schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAlignment Context triple: [WWDC live streams, timeAlignment, synchronized with in‑person WWDC schedule]
-
A.
timeCorrelation
Indicates that two events or states are related in time such that changes or occurrences in one are systematically associated with changes or occurrences in the other.
-
B.
timeCoordinate
Indicates a relationship where a specific time value is used to locate or reference an event, state, or object along a temporal axis or timeline.
-
C.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
-
D.
timingStandard
chosen
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
E.
timeInterpretation
Indicates how a given temporal expression or event should be understood or interpreted in terms of time (e.g., its reference point, scope, or temporal role).
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.