Triple
T5623841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference All-Stars |
E147671
|
entity |
| Predicate | hasRosterChangeFrequency |
P56156
|
FINISHED |
| Object | yearly |
—
|
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: yearly | Statement: [Western Conference All-Stars, hasRosterChangeFrequency, yearly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRosterChangeFrequency Context triple: [Western Conference All-Stars, hasRosterChangeFrequency, yearly]
-
A.
hasCommunicationFrequency
Indicates how often communication occurs between the related entities.
-
B.
typicalUpdateFrequency
chosen
Indicates how often an entity is usually updated or refreshed over time.
-
C.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
D.
hasEventFrequency
Indicates how often a particular event occurs within a given time period.
-
E.
frequentSettingType
Indicates that an entity commonly or regularly occurs, operates, or is used in a particular type of setting or environment.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02214b4948190b71a9f59499092f6 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.