Triple
T38635393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semi-Annual Enterprise Channel |
E937561
|
entity |
| Predicate | hasUpdateCadence |
P71451
|
FINISHED |
| Object | twice per year |
—
|
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: twice per year | Statement: [Semi-Annual Enterprise Channel, hasUpdateCadence, twice per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpdateCadence Context triple: [Semi-Annual Enterprise Channel, hasUpdateCadence, twice per year]
-
A.
hasCadence
Indicates that something possesses or exhibits a particular rhythmic pattern, tempo, or flow.
-
B.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
C.
hasUpdatePolicy
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
-
D.
updatedEvery
chosen
Indicates that something is refreshed or brought up to date at a regular, specified interval.
-
E.
isUpdatedWhen
Indicates that one entity undergoes a change or refresh whenever another specified entity is modified or updated.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.