Triple
T38079720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC Western Division vs SEC Eastern Division |
E950817
|
entity |
| Predicate | typicalScheduleFrequency |
—
|
GENERATED |
| Object | annual meetings between divisions |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScheduleFrequency Context triple: [SEC Western Division vs SEC Eastern Division, typicalScheduleFrequency, annual meetings between divisions]
-
A.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
B.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
C.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
D.
typicalUpdateFrequency
Indicates how often an entity is usually updated or refreshed over time.
-
E.
schedulePattern
chosen
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
- F. None of above.
Provenance (1 batch)
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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.